Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0404bf7e3bd181a6c839dd0bee7c00018f0a0233444dc2df4fd2bd30a1ce4e5f

Tx prefix hash: 2ba2ff7bcd9b308ccfd190e536d2c306ee67db1f4cb41e0746b6cf50af691030
Tx public key: 2c749c1518869459955de59a3ba5a9d6dfc92cc8f4f778235d4c1e18b2f8a71d
Timestamp: 1706292421 Timestamp [UCT]: 2024-01-26 18:07:01 Age [y:d:h:m:s]: 01:076:03:08:12
Block: 943884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315517 RingCT/type: yes/0
Extra: 012c749c1518869459955de59a3ba5a9d6dfc92cc8f4f778235d4c1e18b2f8a71d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 917fba262b127ffe8fbc12a8765c2f07f328dd0a092ce489fc2b05368f0ef2eb 0.600000000000 1402110 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": 943894, "vin": [ { "gen": { "height": 943884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "917fba262b127ffe8fbc12a8765c2f07f328dd0a092ce489fc2b05368f0ef2eb" } } ], "extra": [ 1, 44, 116, 156, 21, 24, 134, 148, 89, 149, 93, 229, 154, 59, 165, 169, 214, 223, 201, 44, 200, 244, 247, 120, 35, 93, 76, 30, 24, 178, 248, 167, 29, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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