Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60ad802577c5dc70597c460dce6f4e9a19e668655b68b3da7843dfac9275ec9f

Tx prefix hash: 0b8828fbe83972e2e9d3c9a4bcd152476c0689fb49e43c21508f5f519c2702e8
Tx public key: 39e10dff8bff08ec2700df3be69b842c95613f8fc42c3388173a3d6dee650850
Timestamp: 1704507056 Timestamp [UCT]: 2024-01-06 02:10:56 Age [y:d:h:m:s]: 01:159:06:34:27
Block: 929080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374960 RingCT/type: yes/0
Extra: 0139e10dff8bff08ec2700df3be69b842c95613f8fc42c3388173a3d6dee65085002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5faeb5c0120727fb52987b0bd158713252eadf5deb99c1bbc11f4b7cd3f5c30 0.600000000000 1386948 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": 929090, "vin": [ { "gen": { "height": 929080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5faeb5c0120727fb52987b0bd158713252eadf5deb99c1bbc11f4b7cd3f5c30" } } ], "extra": [ 1, 57, 225, 13, 255, 139, 255, 8, 236, 39, 0, 223, 59, 230, 155, 132, 44, 149, 97, 63, 143, 196, 44, 51, 136, 23, 58, 61, 109, 238, 101, 8, 80, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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