Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aef17e3f3e7cc9b531c5ab824e9fbe55c505d5f6fee9041ae8829258a2f649c

Tx prefix hash: 53ce17132d8ea404da6273f8940189dee95eadb4b02c2ba3d2358bd70454d2f3
Tx public key: 6a0b9571eea3ef7c7643a45189684230041f542274c3e23e2b29e1c34647bd18
Timestamp: 1716906643 Timestamp [UCT]: 2024-05-28 14:30:43 Age [y:d:h:m:s]: 00:155:23:04:05
Block: 1031922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111633 RingCT/type: yes/0
Extra: 016a0b9571eea3ef7c7643a45189684230041f542274c3e23e2b29e1c34647bd180211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23cb2a75f592a66217d117bdab5ef229ddc7feaaed990c46b35096adb2ffc65b 0.600000000000 1500371 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": 1031932, "vin": [ { "gen": { "height": 1031922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23cb2a75f592a66217d117bdab5ef229ddc7feaaed990c46b35096adb2ffc65b" } } ], "extra": [ 1, 106, 11, 149, 113, 238, 163, 239, 124, 118, 67, 164, 81, 137, 104, 66, 48, 4, 31, 84, 34, 116, 195, 226, 62, 43, 41, 225, 195, 70, 71, 189, 24, 2, 17, 0, 0, 0, 4, 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