Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb33d87626d33d4150dbdad2c21e2e0ffe8bb93f5b0e79fbcc6d8129cacef7da

Tx prefix hash: 8ed42f577381cc0f65b20aea545997f3810ef0416ae38cbdbb4f0e2951849ae8
Tx public key: f18b17ce30dbc8589539022dd77ca97a0a51bb05f3f6373c1f2e48e4223dd692
Timestamp: 1731933984 Timestamp [UCT]: 2024-11-18 12:46:24 Age [y:d:h:m:s]: 01:033:21:52:30
Block: 1156397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282694 RingCT/type: yes/0
Extra: 01f18b17ce30dbc8589539022dd77ca97a0a51bb05f3f6373c1f2e48e4223dd692021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54dc0f45a0b57df396293b3a9da7b212de95fee20f69b54ec402a49eba5b7567 0.600000000000 1642020 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": 1156407, "vin": [ { "gen": { "height": 1156397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54dc0f45a0b57df396293b3a9da7b212de95fee20f69b54ec402a49eba5b7567" } } ], "extra": [ 1, 241, 139, 23, 206, 48, 219, 200, 88, 149, 57, 2, 45, 215, 124, 169, 122, 10, 81, 187, 5, 243, 246, 55, 60, 31, 46, 72, 228, 34, 61, 214, 146, 2, 17, 0, 0, 0, 6, 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