Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffe76545f8c57bb324961970d5e3463be6ecf4f4fcf62a347441cc13d8479322

Tx prefix hash: 611cce1351608fa2eb5fa1c5b71dbf17fee9ed3ffc233e36d64c1e01b698da3d
Tx public key: 83715caa4b54cdf8a8b4fa8d4f8b8a258c0d851b2ce2b4e32515ab3390a807e3
Timestamp: 1749400059 Timestamp [UCT]: 2025-06-08 16:27:39 Age [y:d:h:m:s]: 00:164:09:47:45
Block: 1300747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115190 RingCT/type: yes/0
Extra: 0183715caa4b54cdf8a8b4fa8d4f8b8a258c0d851b2ce2b4e32515ab3390a807e3021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: 757320c350c7d32d69e954b3026f421afde5f4760c99a81ad667caf0c52a1fcb 0.600010000000 1788296 of 0

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": 1300757, "vin": [ { "gen": { "height": 1300747 } } ], "vout": [ { "amount": 600010000, "target": { "key": "757320c350c7d32d69e954b3026f421afde5f4760c99a81ad667caf0c52a1fcb" } } ], "extra": [ 1, 131, 113, 92, 170, 75, 84, 205, 248, 168, 180, 250, 141, 79, 139, 138, 37, 140, 13, 133, 27, 44, 226, 180, 227, 37, 21, 171, 51, 144, 168, 7, 227, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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