Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e68ee093208f5d031583f28f551803e7ea244c86e9868567ad788f6ef35f1e4

Tx prefix hash: 71fcc9cb2748a5e7f859b212d87696d4f5134cf24eed713feb9f156236d2482e
Tx public key: cf50a37fb3c651bf89102ecbd8553e89a7c5663ddb2fdbde5bda3a4014a4c7af
Timestamp: 1686596440 Timestamp [UCT]: 2023-06-12 19:00:40 Age [y:d:h:m:s]: 01:310:08:44:35
Block: 780890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482987 RingCT/type: yes/0
Extra: 01cf50a37fb3c651bf89102ecbd8553e89a7c5663ddb2fdbde5bda3a4014a4c7af0211000000024b8f5122000000000000000000

1 output(s) for total of 1.587038363000 dcy

stealth address amount amount idx
00: 16801e918f487731bdec901939fde1eebcfdc1857ee537041a3faa1f17e0cc4d 1.587038363000 1230627 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": 780900, "vin": [ { "gen": { "height": 780890 } } ], "vout": [ { "amount": 1587038363, "target": { "key": "16801e918f487731bdec901939fde1eebcfdc1857ee537041a3faa1f17e0cc4d" } } ], "extra": [ 1, 207, 80, 163, 127, 179, 198, 81, 191, 137, 16, 46, 203, 216, 85, 62, 137, 167, 197, 102, 61, 219, 47, 219, 222, 91, 218, 58, 64, 20, 164, 199, 175, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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