Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94a2fe78d7d6474f1d6bd1a83387629b3310f5672366d7a993d3c7b7df0e4729

Tx prefix hash: 684a7cbac78ee56fc0012c3f50f77ca21241a284cf10c564988f87fda3ce73b7
Tx public key: 5749eb74295b34dc67cd41ffe8df428f3c8f814f3f531613e27e58a3774b9ae0
Timestamp: 1751955124 Timestamp [UCT]: 2025-07-08 06:12:04 Age [y:d:h:m:s]: 00:207:14:21:13
Block: 1321124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146727 RingCT/type: yes/0
Extra: 015749eb74295b34dc67cd41ffe8df428f3c8f814f3f531613e27e58a3774b9ae00211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab95a24fcf1d7c81a15873583490056e58af05d6f13e884abd1d10448a8ca57b 0.600000000000 1808827 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": 1321134, "vin": [ { "gen": { "height": 1321124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab95a24fcf1d7c81a15873583490056e58af05d6f13e884abd1d10448a8ca57b" } } ], "extra": [ 1, 87, 73, 235, 116, 41, 91, 52, 220, 103, 205, 65, 255, 232, 223, 66, 143, 60, 143, 129, 79, 63, 83, 22, 19, 226, 126, 88, 163, 119, 75, 154, 224, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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