Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c381f3fd16d35d60095f47dc557d80d031230c69d79e78a0da4a55e2e4820d1

Tx prefix hash: def16dd0ed662746ec8abc423a7e080c3163d7892b4dcc6511225202ee3c5ce5
Tx public key: a25ba0ad631da73fb5f1edc8a8381b26dd0196eb4a484721dbb58c22d5bf2d25
Timestamp: 1703663865 Timestamp [UCT]: 2023-12-27 07:57:45 Age [y:d:h:m:s]: 01:022:21:38:56
Block: 922119 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277714 RingCT/type: yes/0
Extra: 01a25ba0ad631da73fb5f1edc8a8381b26dd0196eb4a484721dbb58c22d5bf2d25021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1b71375027a0255caf1b9a37010016ca218f58866e109b77fd7296913717f89 0.600000000000 1379813 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": 922129, "vin": [ { "gen": { "height": 922119 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1b71375027a0255caf1b9a37010016ca218f58866e109b77fd7296913717f89" } } ], "extra": [ 1, 162, 91, 160, 173, 99, 29, 167, 63, 181, 241, 237, 200, 168, 56, 27, 38, 221, 1, 150, 235, 74, 72, 71, 33, 219, 181, 140, 34, 213, 191, 45, 37, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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