Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fc9ca86c7d402beb01220def0928b7091b20571fcb55a110b898f37f27085a6

Tx prefix hash: ca1cbea2ffeb5e535b0de6085c843b26c27e7d97c7fb3e3002be7e7a48796673
Tx public key: 6dba91019a632bb06ee9344aed7d9bf673fd9fc9fe64e2bb9c8f99d8412eb53f
Timestamp: 1763365940 Timestamp [UCT]: 2025-11-17 07:52:20 Age [y:d:h:m:s]: 00:010:22:58:54
Block: 1413949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7851 RingCT/type: yes/0
Extra: 016dba91019a632bb06ee9344aed7d9bf673fd9fc9fe64e2bb9c8f99d8412eb53f021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e0c36fc74f496b093afded8012e93318fa7b399d08a3ac676db0fba924cd27c 0.600000000000 1902432 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": 1413959, "vin": [ { "gen": { "height": 1413949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e0c36fc74f496b093afded8012e93318fa7b399d08a3ac676db0fba924cd27c" } } ], "extra": [ 1, 109, 186, 145, 1, 154, 99, 43, 176, 110, 233, 52, 74, 237, 125, 155, 246, 115, 253, 159, 201, 254, 100, 226, 187, 156, 143, 153, 216, 65, 46, 181, 63, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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