Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5be93855f946c79e1c191b36da24e1a88a3b0f593286873061d35cc9016ea6

Tx prefix hash: a56229edc839b130061a553e267c69fcd04a20db0e635d2bd3fee48ef2f52ce5
Tx public key: bfb7ccaa8c821ed2be1244c80be57284ddfa90dcbf13aa301f0719ab0614d136
Timestamp: 1720834235 Timestamp [UCT]: 2024-07-13 01:30:35 Age [y:d:h:m:s]: 00:266:16:23:01
Block: 1064485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190518 RingCT/type: yes/0
Extra: 01bfb7ccaa8c821ed2be1244c80be57284ddfa90dcbf13aa301f0719ab0614d13602110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfe37dfd9f357d2d9e09dc00b83255989f7e3c3a07d44bffae5e11224deba0e1 0.600000000000 1535012 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": 1064495, "vin": [ { "gen": { "height": 1064485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfe37dfd9f357d2d9e09dc00b83255989f7e3c3a07d44bffae5e11224deba0e1" } } ], "extra": [ 1, 191, 183, 204, 170, 140, 130, 30, 210, 190, 18, 68, 200, 11, 229, 114, 132, 221, 250, 144, 220, 191, 19, 170, 48, 31, 7, 25, 171, 6, 20, 209, 54, 2, 17, 0, 0, 0, 4, 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