Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3001ec45d7c5e62127b4f94a1f69f7ec014d586f203a8ad8ce2856ed1feecdcc

Tx prefix hash: ed8c53dc75be437b09fab6159d2ae95ed13309d02e8bdc8e13103fc37ab4d392
Tx public key: 6fb0f2bce14131c4e3bfef03001aeca1b57c58f084a63618bad5ccbe5c02b6e0
Timestamp: 1699389063 Timestamp [UCT]: 2023-11-07 20:31:03 Age [y:d:h:m:s]: 01:151:01:52:04
Block: 886684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369150 RingCT/type: yes/0
Extra: 016fb0f2bce14131c4e3bfef03001aeca1b57c58f084a63618bad5ccbe5c02b6e00211000000014b8f5122000000000000000000

1 output(s) for total of 0.708023758000 dcy

stealth address amount amount idx
00: d42dd71419795bcdd4ffc2917b75441d49e269c5ddb72e1d154366b0510e4415 0.708023758000 1342517 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": 886694, "vin": [ { "gen": { "height": 886684 } } ], "vout": [ { "amount": 708023758, "target": { "key": "d42dd71419795bcdd4ffc2917b75441d49e269c5ddb72e1d154366b0510e4415" } } ], "extra": [ 1, 111, 176, 242, 188, 225, 65, 49, 196, 227, 191, 239, 3, 0, 26, 236, 161, 181, 124, 88, 240, 132, 166, 54, 24, 186, 213, 204, 190, 92, 2, 182, 224, 2, 17, 0, 0, 0, 1, 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