Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0097dc0b4fa2b0b83592e9cfbd5a99141cbddf4025e3959174b92c0ba852efb

Tx prefix hash: 22535fa03cc65cda0c4ed2ba94b83a468e6b5cbaf80b07e1136c7c6664df876a
Tx public key: 4226e3a16a5b8320dd8037d794cc472b7eac606e77880446f94a6c37eb4ca152
Timestamp: 1698522710 Timestamp [UCT]: 2023-10-28 19:51:50 Age [y:d:h:m:s]: 01:155:12:02:56
Block: 879713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372130 RingCT/type: yes/0
Extra: 014226e3a16a5b8320dd8037d794cc472b7eac606e77880446f94a6c37eb4ca15202110000000675e3f0e9000000000000000000

1 output(s) for total of 0.746699152000 dcy

stealth address amount amount idx
00: 024e81057a9d4988a927a45656b83bfd5e616f417cec0d708e55e97cfdeabb32 0.746699152000 1335249 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": 879723, "vin": [ { "gen": { "height": 879713 } } ], "vout": [ { "amount": 746699152, "target": { "key": "024e81057a9d4988a927a45656b83bfd5e616f417cec0d708e55e97cfdeabb32" } } ], "extra": [ 1, 66, 38, 227, 161, 106, 91, 131, 32, 221, 128, 55, 215, 148, 204, 71, 43, 126, 172, 96, 110, 119, 136, 4, 70, 249, 74, 108, 55, 235, 76, 161, 82, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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