Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 666dc8c14451d21a33913079a8c8f5df95eae34a172972fc0b7498d4b4c1681e

Tx prefix hash: 5922e1f305bdd0f06302a2f9e56693fc0d7819818d346770624622806ddf396f
Tx public key: e6d0ed4436fcea8c30b908c6f852f3eecba4f6a5f7ccfb8b1d2e25708dc4c115
Timestamp: 1754427026 Timestamp [UCT]: 2025-08-05 20:50:26 Age [y:d:h:m:s]: 00:107:10:54:24
Block: 1341010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75789 RingCT/type: yes/0
Extra: 01e6d0ed4436fcea8c30b908c6f852f3eecba4f6a5f7ccfb8b1d2e25708dc4c115021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 231c4801f836c3ab96c655195247f7d9a5e8bc12fdc58d6cfececa9b47a2f34f 0.600000000000 1828831 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": 1341020, "vin": [ { "gen": { "height": 1341010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "231c4801f836c3ab96c655195247f7d9a5e8bc12fdc58d6cfececa9b47a2f34f" } } ], "extra": [ 1, 230, 208, 237, 68, 54, 252, 234, 140, 48, 185, 8, 198, 248, 82, 243, 238, 203, 164, 246, 165, 247, 204, 251, 139, 29, 46, 37, 112, 141, 196, 193, 21, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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