Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8af74f2f46a19e0b4e87baa19833e0c659f74f7ae81bb23ecbcc5d57002e3fad

Tx prefix hash: 2fb4d507640869893499fc4b3ec5a83fbde3de1d56d79d72d4d5b58cb6c0c549
Tx public key: c947208c682d03b463d62fd24b416dd4534b07cd77a40b60dd7175fd6ff1b583
Timestamp: 1744667385 Timestamp [UCT]: 2025-04-14 21:49:45 Age [y:d:h:m:s]: 00:028:00:09:23
Block: 1261552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20035 RingCT/type: yes/0
Extra: 01c947208c682d03b463d62fd24b416dd4534b07cd77a40b60dd7175fd6ff1b583021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee377e632866165551f1d27f0b7879612f4eb205e2b8fdf807488ac7a49e93c8 0.600000000000 1748725 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": 1261562, "vin": [ { "gen": { "height": 1261552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee377e632866165551f1d27f0b7879612f4eb205e2b8fdf807488ac7a49e93c8" } } ], "extra": [ 1, 201, 71, 32, 140, 104, 45, 3, 180, 99, 214, 47, 210, 75, 65, 109, 212, 83, 75, 7, 205, 119, 164, 11, 96, 221, 113, 117, 253, 111, 241, 181, 131, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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