Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd0bd13ffa8669d8607be7df06e1dcbb61cc21a696a3dc4cf1b865e90af269f7

Tx prefix hash: 866cc612b629fb202fbe4ea4a00e6aa7293ec6756e10b4b14f9f2247cfd49abf
Tx public key: 6c8eaf3b06a1814128e4f16d4dfcff18117422b5daf098749114c52dcb361c68
Timestamp: 1741642321 Timestamp [UCT]: 2025-03-10 21:32:01 Age [y:d:h:m:s]: 00:249:02:36:30
Block: 1236524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175769 RingCT/type: yes/0
Extra: 016c8eaf3b06a1814128e4f16d4dfcff18117422b5daf098749114c52dcb361c6802110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9a4a4c631ef312f4d01787f12d9cf7d312b6c2a95e36b86fbc99e4d2bf8207a 0.600000000000 1723471 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": 1236534, "vin": [ { "gen": { "height": 1236524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9a4a4c631ef312f4d01787f12d9cf7d312b6c2a95e36b86fbc99e4d2bf8207a" } } ], "extra": [ 1, 108, 142, 175, 59, 6, 161, 129, 65, 40, 228, 241, 109, 77, 252, 255, 24, 17, 116, 34, 181, 218, 240, 152, 116, 145, 20, 197, 45, 203, 54, 28, 104, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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