Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63ba121f0def4b4166dd730e873656f8821d89f95b72e565107c1d34b0b92c43

Tx prefix hash: 9d9e857e35ce2b69d1a6a1ceccab15b93981af2f37b83ffbfd3f75d04afca0f4
Tx public key: 87dbaad7d574a0f9c8f8b56b61981fe7e21f6d4cf47e3a301f732e8a8791c7e0
Timestamp: 1754459622 Timestamp [UCT]: 2025-08-06 05:53:42 Age [y:d:h:m:s]: 00:055:13:42:25
Block: 1341274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38648 RingCT/type: yes/0
Extra: 0187dbaad7d574a0f9c8f8b56b61981fe7e21f6d4cf47e3a301f732e8a8791c7e00211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16c2c27bcc0fb5ec14c2337e72b0d604040e278be532a573728c91f7615d0ce2 0.600000000000 1829097 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": 1341284, "vin": [ { "gen": { "height": 1341274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16c2c27bcc0fb5ec14c2337e72b0d604040e278be532a573728c91f7615d0ce2" } } ], "extra": [ 1, 135, 219, 170, 215, 213, 116, 160, 249, 200, 248, 181, 107, 97, 152, 31, 231, 226, 31, 109, 76, 244, 126, 58, 48, 31, 115, 46, 138, 135, 145, 199, 224, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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