Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 540e974270b57df45ad98db7c9cfb4f17530bb6d2d8f35d6fb021d3f4028d330

Tx prefix hash: 071c90cdd11682d568473886ebccdb77e34f223bf280902a99a08714481d4561
Tx public key: 93a09b185287a3aa318cdc7955fb50aab0cd18f6db946e1986d9b75e2f539df9
Timestamp: 1760579919 Timestamp [UCT]: 2025-10-16 01:58:39 Age [y:d:h:m:s]: 00:085:04:01:23
Block: 1390862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60988 RingCT/type: yes/0
Extra: 0193a09b185287a3aa318cdc7955fb50aab0cd18f6db946e1986d9b75e2f539df90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 737659c1e5c75a5790e80c87c455b28a24521e6bf0531d5848b9fae3d53d0210 0.600000000000 1879109 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": 1390872, "vin": [ { "gen": { "height": 1390862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "737659c1e5c75a5790e80c87c455b28a24521e6bf0531d5848b9fae3d53d0210" } } ], "extra": [ 1, 147, 160, 155, 24, 82, 135, 163, 170, 49, 140, 220, 121, 85, 251, 80, 170, 176, 205, 24, 246, 219, 148, 110, 25, 134, 217, 183, 94, 47, 83, 157, 249, 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