Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42ca94d95ca425fa5d29223361a685eb2c6cac8f383a172875caf44853cd1b9f

Tx prefix hash: 0aa7b9b671b5d13ac7512d59a959e8fa242e9aba12a6f366e223ac3180afd133
Tx public key: e455431e6bc8739c8d9608c137aa11f02cdcbd51501544f0a1f5670e929f348b
Timestamp: 1750452534 Timestamp [UCT]: 2025-06-20 20:48:54 Age [y:d:h:m:s]: 00:152:11:12:35
Block: 1309282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106825 RingCT/type: yes/0
Extra: 01e455431e6bc8739c8d9608c137aa11f02cdcbd51501544f0a1f5670e929f348b021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52bb3bbd39228ec13a384352ee9116aee242fe01a6ec7a39f9a9a59cecaa30ac 0.600000000000 1796897 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": 1309292, "vin": [ { "gen": { "height": 1309282 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52bb3bbd39228ec13a384352ee9116aee242fe01a6ec7a39f9a9a59cecaa30ac" } } ], "extra": [ 1, 228, 85, 67, 30, 107, 200, 115, 156, 141, 150, 8, 193, 55, 170, 17, 240, 44, 220, 189, 81, 80, 21, 68, 240, 161, 245, 103, 14, 146, 159, 52, 139, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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