Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc6cea62bf9b0368dbe58e4a7ca136ed32a182c0bf0279c86d34ee8722349312

Tx prefix hash: d34c66f69f143a02d9e41864be98dfea9785f6b7f2e3f9244d3b89d165e362c4
Tx public key: a8b40a2f13be3492196aacf57f5105bdb56ee5a32036145a4b1d8ba19c2cdc07
Timestamp: 1751492071 Timestamp [UCT]: 2025-07-02 21:34:31 Age [y:d:h:m:s]: 00:130:00:30:44
Block: 1317494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91163 RingCT/type: yes/0
Extra: 01a8b40a2f13be3492196aacf57f5105bdb56ee5a32036145a4b1d8ba19c2cdc07021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10d861c940f0379e7a441229c70e6f88adcc2fe92e073406444065c499fef333 0.600000000000 1805161 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": 1317504, "vin": [ { "gen": { "height": 1317494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10d861c940f0379e7a441229c70e6f88adcc2fe92e073406444065c499fef333" } } ], "extra": [ 1, 168, 180, 10, 47, 19, 190, 52, 146, 25, 106, 172, 245, 127, 81, 5, 189, 181, 110, 229, 163, 32, 54, 20, 90, 75, 29, 139, 161, 156, 44, 220, 7, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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