Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f308254a21cdedfef16509131ba8da2a8b0080be859c7ed68519f54f5d71704

Tx prefix hash: adeff83e83c0300a62f41def8ada96fa753c79e065adcd8acb000267ea5f7cae
Tx public key: bf9a85ac9d3f0306f8e3b42bf60b4a6b657ebaab3b04a2dd49878e37c4b2c16c
Timestamp: 1709298393 Timestamp [UCT]: 2024-03-01 13:06:33 Age [y:d:h:m:s]: 01:244:06:39:27
Block: 968835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433311 RingCT/type: yes/0
Extra: 01bf9a85ac9d3f0306f8e3b42bf60b4a6b657ebaab3b04a2dd49878e37c4b2c16c0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9753f1e98b4c5fd662d8188b030e59488e805788166f99e090b481db64d59e3 0.600000000000 1428658 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": 968845, "vin": [ { "gen": { "height": 968835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9753f1e98b4c5fd662d8188b030e59488e805788166f99e090b481db64d59e3" } } ], "extra": [ 1, 191, 154, 133, 172, 157, 63, 3, 6, 248, 227, 180, 43, 246, 11, 74, 107, 101, 126, 186, 171, 59, 4, 162, 221, 73, 135, 142, 55, 196, 178, 193, 108, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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