Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63e8fcf4ecdc74554d3f561b1c84d205af9bbd6a2a346b9256b894d2234d9c5f

Tx prefix hash: 8ff113e3c5fe113779e87b000b5c1c6f3eb6510799b2e9808d81eb9905415c8f
Tx public key: c8f4e4079a5122221ad967566e411882e9e34866ce1a264473a8afad6596de53
Timestamp: 1737141971 Timestamp [UCT]: 2025-01-17 19:26:11 Age [y:d:h:m:s]: 00:338:05:44:47
Block: 1199525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239291 RingCT/type: yes/0
Extra: 01c8f4e4079a5122221ad967566e411882e9e34866ce1a264473a8afad6596de530211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40183e7a3b835b01da12f8fbb5ba9dc55ac253df44f2b4a25d3eae9bd95719e4 0.600000000000 1686156 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": 1199535, "vin": [ { "gen": { "height": 1199525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40183e7a3b835b01da12f8fbb5ba9dc55ac253df44f2b4a25d3eae9bd95719e4" } } ], "extra": [ 1, 200, 244, 228, 7, 154, 81, 34, 34, 26, 217, 103, 86, 110, 65, 24, 130, 233, 227, 72, 102, 206, 26, 38, 68, 115, 168, 175, 173, 101, 150, 222, 83, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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