Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 665252e4d5eb8f7f916282ecef114d818fea7899e5610113ba53867d62687a54

Tx prefix hash: 6a40824ac32a332bae0ef4597cb9513063b751516ce2fd67f4eda44a4f0e74e5
Tx public key: a332873bd069fd0040d17ce23a6bff07e125a0ebd0cc6a4b340ae3c8ab92c30c
Timestamp: 1705592198 Timestamp [UCT]: 2024-01-18 15:36:38 Age [y:d:h:m:s]: 01:141:11:43:34
Block: 938094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362255 RingCT/type: yes/0
Extra: 01a332873bd069fd0040d17ce23a6bff07e125a0ebd0cc6a4b340ae3c8ab92c30c02110000001759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94936ac209c9f86f4b20b6040da6110f2bbe061b615b2339eb20b6474fab2865 0.600000000000 1396160 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": 938104, "vin": [ { "gen": { "height": 938094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94936ac209c9f86f4b20b6040da6110f2bbe061b615b2339eb20b6474fab2865" } } ], "extra": [ 1, 163, 50, 135, 59, 208, 105, 253, 0, 64, 209, 124, 226, 58, 107, 255, 7, 225, 37, 160, 235, 208, 204, 106, 75, 52, 10, 227, 200, 171, 146, 195, 12, 2, 17, 0, 0, 0, 23, 89, 218, 211, 245, 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