Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e73d31e8182375a4f34baa6c42ec2dfa5b69bf97341cfaf70c87df412d64b205

Tx prefix hash: 663e663b11dbb8d3df297375ebabaf3bf23d46c174244787caaa2738d649dd6a
Tx public key: 41902ea9e061f8f612c6a3701eb8ecb9ad675eae27c1a90d28543dc040712217
Timestamp: 1730153020 Timestamp [UCT]: 2024-10-28 22:03:40 Age [y:d:h:m:s]: 00:170:09:47:20
Block: 1141659 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121621 RingCT/type: yes/0
Extra: 0141902ea9e061f8f612c6a3701eb8ecb9ad675eae27c1a90d28543dc0407122170211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93de060ab636e4c9a968e7e97584e46425b8ccaa9936fe28aa7fa06d645cff6f 0.600000000000 1625470 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": 1141669, "vin": [ { "gen": { "height": 1141659 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93de060ab636e4c9a968e7e97584e46425b8ccaa9936fe28aa7fa06d645cff6f" } } ], "extra": [ 1, 65, 144, 46, 169, 224, 97, 248, 246, 18, 198, 163, 112, 30, 184, 236, 185, 173, 103, 94, 174, 39, 193, 169, 13, 40, 84, 61, 192, 64, 113, 34, 23, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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