Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b329155fa9dc5eca7b49aed4efca553b692f98d00744af0844d61dfa11af18f8

Tx prefix hash: 481f22c2d494b47fca2c5561d6aed32bb85ef19ef4ac1ca07c4b8cfbdc70f9fa
Tx public key: 16f4f29e9b5216071e364c7c79943d3e5e550ad1cea0032d93181903de3de8d8
Timestamp: 1726659201 Timestamp [UCT]: 2024-09-18 11:33:21 Age [y:d:h:m:s]: 00:239:13:28:38
Block: 1112764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171055 RingCT/type: yes/0
Extra: 0116f4f29e9b5216071e364c7c79943d3e5e550ad1cea0032d93181903de3de8d802110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a04276a63cdf57575fe43d9a9d22c36c734dd70588506f51bd1323b9a01924f5 0.600000000000 1592199 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": 1112774, "vin": [ { "gen": { "height": 1112764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a04276a63cdf57575fe43d9a9d22c36c734dd70588506f51bd1323b9a01924f5" } } ], "extra": [ 1, 22, 244, 242, 158, 155, 82, 22, 7, 30, 54, 76, 124, 121, 148, 61, 62, 94, 85, 10, 209, 206, 160, 3, 45, 147, 24, 25, 3, 222, 61, 232, 216, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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