Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01bd247de4b623c8b30ba31512e10d661cdfb9a05c33bc09e5c74153acead187

Tx prefix hash: 82ea7301215031e46ff5ffaf58ba8e266419c493426e71bf5c1ba9238f4e5307
Tx public key: d49730d0b066cb10b863607e9b5e9536725ef9a136f962a9ba0c6c382cfd48b1
Timestamp: 1728906850 Timestamp [UCT]: 2024-10-14 11:54:10 Age [y:d:h:m:s]: 00:100:03:00:17
Block: 1131406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71517 RingCT/type: yes/0
Extra: 01d49730d0b066cb10b863607e9b5e9536725ef9a136f962a9ba0c6c382cfd48b1021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13fbcfdef655fe2ce262b80364fc8a0b839cda16fe6af9d4fee2d185098db46e 0.600000000000 1614305 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": 1131416, "vin": [ { "gen": { "height": 1131406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13fbcfdef655fe2ce262b80364fc8a0b839cda16fe6af9d4fee2d185098db46e" } } ], "extra": [ 1, 212, 151, 48, 208, 176, 102, 203, 16, 184, 99, 96, 126, 155, 94, 149, 54, 114, 94, 249, 161, 54, 249, 98, 169, 186, 12, 108, 56, 44, 253, 72, 177, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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