Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39abae15a2e1625451f7d77962104c69b0ac2dea2535caf580b888b13414a82b

Tx prefix hash: 2a5c698509f0ff002aaa10a4bf4fcf7ea5c2e16feda42ea8e9938e4780a7e2f4
Tx public key: 377c09fc603d932bb7f381deac50ea65c416cf52413a5207a806a12bbb08b1a0
Timestamp: 1737673325 Timestamp [UCT]: 2025-01-23 23:02:05 Age [y:d:h:m:s]: 00:150:03:30:07
Block: 1203876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106967 RingCT/type: yes/0
Extra: 01377c09fc603d932bb7f381deac50ea65c416cf52413a5207a806a12bbb08b1a0021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f100d7e28dbbcf6890188c075edb37f78343207591317443f9f5121383d4a1b0 0.600000000000 1690557 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": 1203886, "vin": [ { "gen": { "height": 1203876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f100d7e28dbbcf6890188c075edb37f78343207591317443f9f5121383d4a1b0" } } ], "extra": [ 1, 55, 124, 9, 252, 96, 61, 147, 43, 183, 243, 129, 222, 172, 80, 234, 101, 196, 22, 207, 82, 65, 58, 82, 7, 168, 6, 161, 43, 187, 8, 177, 160, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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