Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02f2863b3c0a9493d17292f3c3213a484403b79d708cc13febc4ed743559a78a

Tx prefix hash: 6697a377eea2a5ac753f32b4ea94bab1dd9a88812cb8d8b7de8de6866e615765
Tx public key: 45360df5f10a7787628af16b156672b85903d1dc007872f252f05231f03c7dff
Timestamp: 1706710306 Timestamp [UCT]: 2024-01-31 14:11:46 Age [y:d:h:m:s]: 01:118:05:59:29
Block: 947357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345635 RingCT/type: yes/0
Extra: 0145360df5f10a7787628af16b156672b85903d1dc007872f252f05231f03c7dff0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe980299f81f3a34cb7bcbf5b7f3be4ee8b99a5e87623063c1dac2e5af71b36b 0.600000000000 1405705 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": 947367, "vin": [ { "gen": { "height": 947357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe980299f81f3a34cb7bcbf5b7f3be4ee8b99a5e87623063c1dac2e5af71b36b" } } ], "extra": [ 1, 69, 54, 13, 245, 241, 10, 119, 135, 98, 138, 241, 107, 21, 102, 114, 184, 89, 3, 209, 220, 0, 120, 114, 242, 82, 240, 82, 49, 240, 60, 125, 255, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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