Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16666c31127624a5b5ff100dac0c60accbeaa05091df6f3b06d9c89c6bf61c10

Tx prefix hash: 8856cc766d4930903c0658dda3edecab6d753b61755cfd4cd82b98d5dacdc3fa
Tx public key: aa18273336b933404164ec67823721dcc95959aa431a1a5ecaca6b248d0623d2
Timestamp: 1696833548 Timestamp [UCT]: 2023-10-09 06:39:08 Age [y:d:h:m:s]: 01:177:13:43:19
Block: 865707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387931 RingCT/type: yes/0
Extra: 01aa18273336b933404164ec67823721dcc95959aa431a1a5ecaca6b248d0623d2021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.830908823000 dcy

stealth address amount amount idx
00: 38c66c2d40e2ef9f0303b8a23c2de8cf7d966ba6ae49dc0924fd63ef013347fc 0.830908823000 1320249 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": 865717, "vin": [ { "gen": { "height": 865707 } } ], "vout": [ { "amount": 830908823, "target": { "key": "38c66c2d40e2ef9f0303b8a23c2de8cf7d966ba6ae49dc0924fd63ef013347fc" } } ], "extra": [ 1, 170, 24, 39, 51, 54, 185, 51, 64, 65, 100, 236, 103, 130, 55, 33, 220, 201, 89, 89, 170, 67, 26, 26, 94, 202, 202, 107, 36, 141, 6, 35, 210, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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