Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20071765b22d62efb26a766e31103c2990341ea54d9deb856c0a1f2679c2e357

Tx prefix hash: a03596cd6504a601594494fc64c4545c4c0f6164733f61f0f7fe55aad42a7b83
Tx public key: c0b38cf25b1c9cb9119eb653780d719698b580f3162c5c59842f45d5c8fb1016
Timestamp: 1701044258 Timestamp [UCT]: 2023-11-27 00:17:38 Age [y:d:h:m:s]: 01:166:11:51:37
Block: 900398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380184 RingCT/type: yes/0
Extra: 01c0b38cf25b1c9cb9119eb653780d719698b580f3162c5c59842f45d5c8fb101602110000000b33af99f4000000000000000000

1 output(s) for total of 0.637687106000 dcy

stealth address amount amount idx
00: 4d2595597a2113b0306ec6cda1419d7ca34c4bc1009e1650b3a05dcbaa330e69 0.637687106000 1356899 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": 900408, "vin": [ { "gen": { "height": 900398 } } ], "vout": [ { "amount": 637687106, "target": { "key": "4d2595597a2113b0306ec6cda1419d7ca34c4bc1009e1650b3a05dcbaa330e69" } } ], "extra": [ 1, 192, 179, 140, 242, 91, 28, 156, 185, 17, 158, 182, 83, 120, 13, 113, 150, 152, 181, 128, 243, 22, 44, 92, 89, 132, 47, 69, 213, 200, 251, 16, 22, 2, 17, 0, 0, 0, 11, 51, 175, 153, 244, 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