Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9a977bd91aca4ede01ee4e8418c1b59d5d3bd7a53cb627231c3d520dd1a34f92

Tx prefix hash: 06ffedcd6133b7d8f5d3e16f7787764afe5415fd1b038240b303a6cd76ff48c1
Tx public key: 0f0683e92a2ad155be7a42f1e22fe3b005f5aade2523bca63c8451c19cef0c8d
Timestamp: 1721019434 Timestamp [UCT]: 2024-07-15 04:57:14 Age [y:d:h:m:s]: 00:300:07:20:31
Block: 1066019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214567 RingCT/type: yes/0
Extra: 010f0683e92a2ad155be7a42f1e22fe3b005f5aade2523bca63c8451c19cef0c8d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dda80b5c4db59dc22e012cb37e535de039d264a4102edb22d6972072116ac34 0.600000000000 1536590 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1066029, "vin": [ { "gen": { "height": 1066019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dda80b5c4db59dc22e012cb37e535de039d264a4102edb22d6972072116ac34" } } ], "extra": [ 1, 15, 6, 131, 233, 42, 42, 209, 85, 190, 122, 66, 241, 226, 47, 227, 176, 5, 245, 170, 222, 37, 35, 188, 166, 60, 132, 81, 193, 156, 239, 12, 141, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8