Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342a42931893065a8d6e0153019096a2bc18c311db6ad4d02e24f3fc5a9c602a

Tx prefix hash: 7f12c300ef8671e03dc1f14df73f8d4573d1c76ea65b6bb3a16234b38fdad6ac
Tx public key: e70616f1bbf795a1dab4d7fa10ae9722d7f05e6906b1de0cc8ea25ed219aebf8
Timestamp: 1706620901 Timestamp [UCT]: 2024-01-30 13:21:41 Age [y:d:h:m:s]: 01:287:17:03:25
Block: 946615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464432 RingCT/type: yes/0
Extra: 01e70616f1bbf795a1dab4d7fa10ae9722d7f05e6906b1de0cc8ea25ed219aebf80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 812e1e96d9759ffbb75e0712a3c05da2fac475cefd1234a4cb20b2ef9200e29b 0.600000000000 1404949 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": 946625, "vin": [ { "gen": { "height": 946615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "812e1e96d9759ffbb75e0712a3c05da2fac475cefd1234a4cb20b2ef9200e29b" } } ], "extra": [ 1, 231, 6, 22, 241, 187, 247, 149, 161, 218, 180, 215, 250, 16, 174, 151, 34, 215, 240, 94, 105, 6, 177, 222, 12, 200, 234, 37, 237, 33, 154, 235, 248, 2, 17, 0, 0, 0, 1, 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