Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36c6a605bb67fbf03218693e65382c9a182837e4128309b9217d953b90b9bd1c

Tx prefix hash: db6c2f52b99252b0f9e833a7089d0f27c68e7a7515cbe5069c85408b1556a02f
Tx public key: 430b3fe81e669699c74eae11b4222adbc387ddfa78e931e99f807a4929b3516a
Timestamp: 1675612754 Timestamp [UCT]: 2023-02-05 15:59:14 Age [y:d:h:m:s]: 02:133:20:30:45
Block: 690445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 617212 RingCT/type: yes/0
Extra: 01430b3fe81e669699c74eae11b4222adbc387ddfa78e931e99f807a4929b3516a0211000000035029cbac000000000000000000

1 output(s) for total of 3.164237149000 dcy

stealth address amount amount idx
00: 31be8c757b622dfc50982f8a25e3f8d5ae3b70612ebc7ce967123f043503fe90 3.164237149000 1133173 of 0

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": 690455, "vin": [ { "gen": { "height": 690445 } } ], "vout": [ { "amount": 3164237149, "target": { "key": "31be8c757b622dfc50982f8a25e3f8d5ae3b70612ebc7ce967123f043503fe90" } } ], "extra": [ 1, 67, 11, 63, 232, 30, 102, 150, 153, 199, 78, 174, 17, 180, 34, 42, 219, 195, 135, 221, 250, 120, 233, 49, 233, 159, 128, 122, 73, 41, 179, 81, 106, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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