Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b65a3c2ce89a3806e0999f62b649212fcab56213977a8154e36967c335596f39

Tx prefix hash: a8e1076edf8492cc3bb39aa90be78a363f7fd783f593dc7426103c190f791bc1
Tx public key: 43e3b27c0f4a32899ab0065853fbb9566d0716b5d02f7f90f83c166aaf0770be
Timestamp: 1749638961 Timestamp [UCT]: 2025-06-11 10:49:21 Age [y:d:h:m:s]: 00:155:01:32:33
Block: 1302705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108521 RingCT/type: yes/0
Extra: 0143e3b27c0f4a32899ab0065853fbb9566d0716b5d02f7f90f83c166aaf0770be021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 057b44b0b154bdc1a4f829ad849af0a39a6c1fac31d78a37cc41e7a8b319413a 0.600000000000 1790278 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": 1302715, "vin": [ { "gen": { "height": 1302705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "057b44b0b154bdc1a4f829ad849af0a39a6c1fac31d78a37cc41e7a8b319413a" } } ], "extra": [ 1, 67, 227, 178, 124, 15, 74, 50, 137, 154, 176, 6, 88, 83, 251, 185, 86, 109, 7, 22, 181, 208, 47, 127, 144, 248, 60, 22, 106, 175, 7, 112, 190, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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