Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d707a6bbf09fa6feb9a778b5031c76c68c5b3d49c25942fff25fe53ce6101136

Tx prefix hash: e2b1a32857b290a065043b5cdd3d6738a15efb3835e920d03cb6b6acd6e8c8cf
Tx public key: 2a7333ad4f1e22912221b8eb810406d5c2636b379da64baa8189e1bb58065554
Timestamp: 1758454384 Timestamp [UCT]: 2025-09-21 11:33:04 Age [y:d:h:m:s]: 00:060:12:51:51
Block: 1373254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43328 RingCT/type: yes/0
Extra: 012a7333ad4f1e22912221b8eb810406d5c2636b379da64baa8189e1bb58065554021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a911b08a1527e8bddfce8c7521efc9a32e6091edf822c464d7c9443d12f5813 0.600000000000 1861339 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": 1373264, "vin": [ { "gen": { "height": 1373254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a911b08a1527e8bddfce8c7521efc9a32e6091edf822c464d7c9443d12f5813" } } ], "extra": [ 1, 42, 115, 51, 173, 79, 30, 34, 145, 34, 33, 184, 235, 129, 4, 6, 213, 194, 99, 107, 55, 157, 166, 75, 170, 129, 137, 225, 187, 88, 6, 85, 84, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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