Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2d7a6388d0d33c01ddc69526b71533269ed72b3b614e661bcd70e8c463854f1

Tx prefix hash: 86816344cf31f0e5e8616a2e13ac1a1c79e79ce2b989115ea39394a9862df597
Tx public key: 84217879105168b7924f34024adbab1c8ed2451f5e7f948eb0c32caa7a1687e0
Timestamp: 1662291485 Timestamp [UCT]: 2022-09-04 11:38:05 Age [y:d:h:m:s]: 03:058:02:22:46
Block: 580598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 821379 RingCT/type: yes/0
Extra: 0184217879105168b7924f34024adbab1c8ed2451f5e7f948eb0c32caa7a1687e0021100000004e6d27f9c000000000000000000

1 output(s) for total of 7.315396931000 dcy

stealth address amount amount idx
00: 50db1d1cc6bc4a49be235d1c750ca19fff7f6e6a75e103b18dfa52d5ad712f55 7.315396931000 1014142 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": 580608, "vin": [ { "gen": { "height": 580598 } } ], "vout": [ { "amount": 7315396931, "target": { "key": "50db1d1cc6bc4a49be235d1c750ca19fff7f6e6a75e103b18dfa52d5ad712f55" } } ], "extra": [ 1, 132, 33, 120, 121, 16, 81, 104, 183, 146, 79, 52, 2, 74, 219, 171, 28, 142, 210, 69, 31, 94, 127, 148, 142, 176, 195, 44, 170, 122, 22, 135, 224, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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