Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f024d3a54d8bc92f1f1046365564c98893374acf376c8f019ea856080517a8dd

Tx prefix hash: 0cc05142ae52f39738de6f072e957c83a4a40fa5fb7d41e97bd7e4acc1ac4fad
Tx public key: ae7c978efb4fb40e5773ecd3405574eab71393498b5f4cb7fa3fb8239ba8443e
Timestamp: 1579296334 Timestamp [UCT]: 2020-01-17 21:25:34 Age [y:d:h:m:s]: 04:314:13:09:10
Block: 47851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114206 RingCT/type: yes/0
Extra: 01ae7c978efb4fb40e5773ecd3405574eab71393498b5f4cb7fa3fb8239ba8443e0211000000088a2ee0d9000000000000000000

1 output(s) for total of 426.047578790000 dcy

stealth address amount amount idx
00: 96fc36df9d85fbc03ecb8fe69d40b555d039d9273d6e6fe7447c4f384b4db20d 426.047578790000 88402 of 0

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": 47861, "vin": [ { "gen": { "height": 47851 } } ], "vout": [ { "amount": 426047578790, "target": { "key": "96fc36df9d85fbc03ecb8fe69d40b555d039d9273d6e6fe7447c4f384b4db20d" } } ], "extra": [ 1, 174, 124, 151, 142, 251, 79, 180, 14, 87, 115, 236, 211, 64, 85, 116, 234, 183, 19, 147, 73, 139, 95, 76, 183, 250, 63, 184, 35, 155, 168, 68, 62, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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