Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 366c4dbcf8b9de8fc5d19bf6224df9607bd068e2765786d870cc162190cf2faf

Tx prefix hash: 839dfbc101177c351ca68276dcf8f4d8f603bc00e1fb4e0af74d16243de7a621
Tx public key: 6887c851e00cbd9dafbb9e2a1c4838fdec87b3e8c0021245fac938a8a13d6359
Timestamp: 1761750447 Timestamp [UCT]: 2025-10-29 15:07:27 Age [y:d:h:m:s]: 00:010:08:22:40
Block: 1400578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7393 RingCT/type: yes/0
Extra: 016887c851e00cbd9dafbb9e2a1c4838fdec87b3e8c0021245fac938a8a13d635902110000000825a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd583cb4dbf806287ec24223b492a9622af3b3ccef99016ddc2576f122dfdf21 0.600000000000 1888895 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": 1400588, "vin": [ { "gen": { "height": 1400578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd583cb4dbf806287ec24223b492a9622af3b3ccef99016ddc2576f122dfdf21" } } ], "extra": [ 1, 104, 135, 200, 81, 224, 12, 189, 157, 175, 187, 158, 42, 28, 72, 56, 253, 236, 135, 179, 232, 192, 2, 18, 69, 250, 201, 56, 168, 161, 61, 99, 89, 2, 17, 0, 0, 0, 8, 37, 163, 90, 15, 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