Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0fa2a332e22603b7009d6e6a7ba07912c86931484a4dc1e1c3e41cfc30e03216

Tx prefix hash: 3f5ad597755d115414e502fac6d9937f2c94a6848e13e5ee920d9aab60bd5a44
Tx public key: 2110455237f55fa54937c314a55c66e4085154a2b7315f10d17cce7d8eb0e9f3
Timestamp: 1702235758 Timestamp [UCT]: 2023-12-10 19:15:58 Age [y:d:h:m:s]: 01:031:10:16:13
Block: 910280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283823 RingCT/type: yes/0
Extra: 012110455237f55fa54937c314a55c66e4085154a2b7315f10d17cce7d8eb0e9f3021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b0e6a4b7915740bf4027c346ba6f05fe7a47adcf33cbfbe6ee7550cdbcddfd5 0.600000000000 1367429 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": 910290, "vin": [ { "gen": { "height": 910280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b0e6a4b7915740bf4027c346ba6f05fe7a47adcf33cbfbe6ee7550cdbcddfd5" } } ], "extra": [ 1, 33, 16, 69, 82, 55, 245, 95, 165, 73, 55, 195, 20, 165, 92, 102, 228, 8, 81, 84, 162, 183, 49, 95, 16, 209, 124, 206, 125, 142, 176, 233, 243, 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