Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10d5be416a1c5369b57608f14b0b354c280315823af504039f74f88393dc173e

Tx prefix hash: 5ab66eec927a8f989fb991e6a1c50aad30dd73737ceb1e8a471347532cc07d77
Tx public key: 55d01ca3d57fe9d614ff6c00163fb087b0a60e7e4541f28874bf9d279d91ff2a
Timestamp: 1703980617 Timestamp [UCT]: 2023-12-30 23:56:57 Age [y:d:h:m:s]: 01:116:01:40:27
Block: 924740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344083 RingCT/type: yes/0
Extra: 0155d01ca3d57fe9d614ff6c00163fb087b0a60e7e4541f28874bf9d279d91ff2a0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d1151ae0ccdeb406ee1237f21dc1e49b98ef9d8af62849b8115ac1dd2ac036f 0.600000000000 1382496 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": 924750, "vin": [ { "gen": { "height": 924740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d1151ae0ccdeb406ee1237f21dc1e49b98ef9d8af62849b8115ac1dd2ac036f" } } ], "extra": [ 1, 85, 208, 28, 163, 213, 127, 233, 214, 20, 255, 108, 0, 22, 63, 176, 135, 176, 166, 14, 126, 69, 65, 242, 136, 116, 191, 157, 39, 157, 145, 255, 42, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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