Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 605782ff515a508e1d1df430b98f383c376f19357054637181f213eaf71ccaa5

Tx prefix hash: 44bfcf10ead5e3257e29a09e1ff7969c4ddc8a64e9238503c1ee48e1817c4baa
Tx public key: ccace5aca06ac66f0673d1d99fb967f80311bfde0aa93059b14a7e32928ac4e3
Timestamp: 1722193675 Timestamp [UCT]: 2024-07-28 19:07:55 Age [y:d:h:m:s]: 00:260:09:55:28
Block: 1075741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186027 RingCT/type: yes/0
Extra: 01ccace5aca06ac66f0673d1d99fb967f80311bfde0aa93059b14a7e32928ac4e302110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e1f3cb8252b9420b7e031bb0f7818a6b74540692a5d4bedaafa947f7d6047ff 0.600000000000 1548270 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": 1075751, "vin": [ { "gen": { "height": 1075741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e1f3cb8252b9420b7e031bb0f7818a6b74540692a5d4bedaafa947f7d6047ff" } } ], "extra": [ 1, 204, 172, 229, 172, 160, 106, 198, 111, 6, 115, 209, 217, 159, 185, 103, 248, 3, 17, 191, 222, 10, 169, 48, 89, 177, 74, 126, 50, 146, 138, 196, 227, 2, 17, 0, 0, 0, 20, 145, 225, 60, 4, 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