Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63826548940d17b5fd185f6f100cb4cc47767cedd2d2e40717fd5e955dce0402

Tx prefix hash: 6ae071a61c9d4d97e575dde0323833b24e57c5e6a9c775cca6add6a042275b02
Tx public key: e04d429de56f5e11c70bbf33dc04391e7b89815f5d96e7f6c21ea090102741d5
Timestamp: 1757906378 Timestamp [UCT]: 2025-09-15 03:19:38 Age [y:d:h:m:s]: 00:137:16:30:41
Block: 1368707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98406 RingCT/type: yes/0
Extra: 01e04d429de56f5e11c70bbf33dc04391e7b89815f5d96e7f6c21ea090102741d5021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6c2d17ab46a8a7d9d88d6839eaf6fbafbb6ef2d617c4f14c5a520e1d2e06cc1 0.600000000000 1856758 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": 1368717, "vin": [ { "gen": { "height": 1368707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6c2d17ab46a8a7d9d88d6839eaf6fbafbb6ef2d617c4f14c5a520e1d2e06cc1" } } ], "extra": [ 1, 224, 77, 66, 157, 229, 111, 94, 17, 199, 11, 191, 51, 220, 4, 57, 30, 123, 137, 129, 95, 93, 150, 231, 246, 194, 30, 160, 144, 16, 39, 65, 213, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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