Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44663ead0c5daf7e263656ee872fde9ef110c489967815ea3e5b1f848241fb73

Tx prefix hash: dc9b6c8c9410bbc6cc268c7c9a52288db8608527717c4bf7d8f54d3da8280d17
Tx public key: 61c6078e0c3ab9e3731bbe81b9ffc1c725fcff01ed04fcd4bf17637c52a0b2a2
Timestamp: 1705615782 Timestamp [UCT]: 2024-01-18 22:09:42 Age [y:d:h:m:s]: 01:083:07:50:04
Block: 938289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320654 RingCT/type: yes/0
Extra: 0161c6078e0c3ab9e3731bbe81b9ffc1c725fcff01ed04fcd4bf17637c52a0b2a202110000000882025268000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acbd5b4a6444ef49965fa23cb3e578e0d0092e39fafb3db09069ae992fa07131 0.600000000000 1396359 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": 938299, "vin": [ { "gen": { "height": 938289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acbd5b4a6444ef49965fa23cb3e578e0d0092e39fafb3db09069ae992fa07131" } } ], "extra": [ 1, 97, 198, 7, 142, 12, 58, 185, 227, 115, 27, 190, 129, 185, 255, 193, 199, 37, 252, 255, 1, 237, 4, 252, 212, 191, 23, 99, 124, 82, 160, 178, 162, 2, 17, 0, 0, 0, 8, 130, 2, 82, 104, 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