Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c8959415de5242ef17717deece57528fc99b3745221e05c00d0933e6c5f7fc6

Tx prefix hash: 848f332a4c23aefbffeff19f9deee112be79252207f2d9d21df241d82e751628
Tx public key: 0e59fb2307e8fed7cb278ed798d8e755b7b44c23deab14a20473f3a78cc11486
Timestamp: 1673113962 Timestamp [UCT]: 2023-01-07 17:52:42 Age [y:d:h:m:s]: 02:100:00:29:15
Block: 669705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593173 RingCT/type: yes/0
Extra: 010e59fb2307e8fed7cb278ed798d8e755b7b44c23deab14a20473f3a78cc11486021100000005faf35c9c000000000000000000

1 output(s) for total of 3.706715763000 dcy

stealth address amount amount idx
00: b248c02893d6d3e751cfd5d8aee527308999d3d35a6e1539dfb43ef5a3a0571e 3.706715763000 1111062 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": 669715, "vin": [ { "gen": { "height": 669705 } } ], "vout": [ { "amount": 3706715763, "target": { "key": "b248c02893d6d3e751cfd5d8aee527308999d3d35a6e1539dfb43ef5a3a0571e" } } ], "extra": [ 1, 14, 89, 251, 35, 7, 232, 254, 215, 203, 39, 142, 215, 152, 216, 231, 85, 183, 180, 76, 35, 222, 171, 20, 162, 4, 115, 243, 167, 140, 193, 20, 134, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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