Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a0348148c7748414fb8f23cda89bb3c75b6d6002a142d3f2d472f9ff0472a0c

Tx prefix hash: 78638d20432fbe15562e7513f0b522225aac5d7447ee950fb47ab37acb0ad2f4
Tx public key: b528d16cd55b203395f559024a5f9fadc9d5fc32f3838e3e64596e7afa6b8242
Timestamp: 1761433280 Timestamp [UCT]: 2025-10-25 23:01:20 Age [y:d:h:m:s]: 00:014:19:55:22
Block: 1397942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10613 RingCT/type: yes/0
Extra: 01b528d16cd55b203395f559024a5f9fadc9d5fc32f3838e3e64596e7afa6b824202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c957b7db1e08c983255967bcf0d6e8d528b2ad5834e2024a2b3ee43929f3de4 0.600000000000 1886235 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": 1397952, "vin": [ { "gen": { "height": 1397942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c957b7db1e08c983255967bcf0d6e8d528b2ad5834e2024a2b3ee43929f3de4" } } ], "extra": [ 1, 181, 40, 209, 108, 213, 91, 32, 51, 149, 245, 89, 2, 74, 95, 159, 173, 201, 213, 252, 50, 243, 131, 142, 62, 100, 89, 110, 122, 250, 107, 130, 66, 2, 17, 0, 0, 0, 1, 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