Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8bd3acac867b4ff9f3837fbd506337d0510d00f71755753080bdec8e3b491e9

Tx prefix hash: 7df6d6e08ed4a402f9b9f87eac7624f2dba3b9d9ae587668f2cc1122313c14f6
Tx public key: e0f678802bf8a5511afd57e56bb9942197d9f6f2b741ad623456c82647bdbfb4
Timestamp: 1760700623 Timestamp [UCT]: 2025-10-17 11:30:23 Age [y:d:h:m:s]: 00:067:06:27:21
Block: 1391867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48160 RingCT/type: yes/0
Extra: 01e0f678802bf8a5511afd57e56bb9942197d9f6f2b741ad623456c82647bdbfb40211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 163aec0f7dabc1c94af7fdd66a87ed27bf3b0f9398530b48e188de4b065a6e23 0.600000000000 1880116 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": 1391877, "vin": [ { "gen": { "height": 1391867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "163aec0f7dabc1c94af7fdd66a87ed27bf3b0f9398530b48e188de4b065a6e23" } } ], "extra": [ 1, 224, 246, 120, 128, 43, 248, 165, 81, 26, 253, 87, 229, 107, 185, 148, 33, 151, 217, 246, 242, 183, 65, 173, 98, 52, 86, 200, 38, 71, 189, 191, 180, 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