Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16a5212f0885a5f9e20c988dab360df0898b0f68188b028ad7801aa21cbe5696

Tx prefix hash: 8a07e5c08fa0e34e5bf6e6b10aa2aedb564fbfca8554f2ea40bd6560fce0994a
Tx public key: 46b55e5c8d58cd46adce0fdd351d7b8c17e8e5bed2e8918ff432bb44a32e77ca
Timestamp: 1676811151 Timestamp [UCT]: 2023-02-19 12:52:31 Age [y:d:h:m:s]: 02:048:06:14:52
Block: 700372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556085 RingCT/type: yes/0
Extra: 0146b55e5c8d58cd46adce0fdd351d7b8c17e8e5bed2e8918ff432bb44a32e77ca02110000000274b6d784000000000000000000

1 output(s) for total of 2.933436817000 dcy

stealth address amount amount idx
00: 496d796326f443ee8e9942eca61ce6286eb983bdec1305d3403741d64930ef1b 2.933436817000 1143813 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": 700382, "vin": [ { "gen": { "height": 700372 } } ], "vout": [ { "amount": 2933436817, "target": { "key": "496d796326f443ee8e9942eca61ce6286eb983bdec1305d3403741d64930ef1b" } } ], "extra": [ 1, 70, 181, 94, 92, 141, 88, 205, 70, 173, 206, 15, 221, 53, 29, 123, 140, 23, 232, 229, 190, 210, 232, 145, 143, 244, 50, 187, 68, 163, 46, 119, 202, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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