Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 871217bef5de7c4bb0bf62d4f47a7d751b681972243e88c03a6b7aeea1be4c17

Tx prefix hash: f68e18ed851f49b278502b518ce8bb47c116a5f4683ecd691496af5e5d79c0a5
Tx public key: 8d044d1d09f9fbe941430c6a4da788b0df854fbe14858ef9b23ea76050eb2504
Timestamp: 1668697205 Timestamp [UCT]: 2022-11-17 15:00:05 Age [y:d:h:m:s]: 02:178:23:17:28
Block: 633157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649645 RingCT/type: yes/0
Extra: 018d044d1d09f9fbe941430c6a4da788b0df854fbe14858ef9b23ea76050eb250402110000000183600029000000000000000000

1 output(s) for total of 4.898781107000 dcy

stealth address amount amount idx
00: 64b05d0ebd6f91d056235931bfc0df27cdae54f264f99b2b92029610458d8dfa 4.898781107000 1072203 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": 633167, "vin": [ { "gen": { "height": 633157 } } ], "vout": [ { "amount": 4898781107, "target": { "key": "64b05d0ebd6f91d056235931bfc0df27cdae54f264f99b2b92029610458d8dfa" } } ], "extra": [ 1, 141, 4, 77, 29, 9, 249, 251, 233, 65, 67, 12, 106, 77, 167, 136, 176, 223, 133, 79, 190, 20, 133, 142, 249, 178, 62, 167, 96, 80, 235, 37, 4, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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