Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa09cd2b65b6cf3374d7fbc867e5058ec912c13daf32ce5cc8364cf9a04a7232

Tx prefix hash: 0e2b7eb5fe84a9ac17cd75695024cb5fb876d4f69e10f44860b631a2fd42c354
Tx public key: 0ed66eb006650a3d9ceb5888a2bf593212137a3d9ea1a23038005aea4c95a952
Timestamp: 1736991307 Timestamp [UCT]: 2025-01-16 01:35:07 Age [y:d:h:m:s]: 00:334:20:18:44
Block: 1198273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236860 RingCT/type: yes/0
Extra: 010ed66eb006650a3d9ceb5888a2bf593212137a3d9ea1a23038005aea4c95a952021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7abd787c1aa479d2905cbc98ada7378c2acd80a19bc473c55999e91a74e25d2 0.600000000000 1684894 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": 1198283, "vin": [ { "gen": { "height": 1198273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7abd787c1aa479d2905cbc98ada7378c2acd80a19bc473c55999e91a74e25d2" } } ], "extra": [ 1, 14, 214, 110, 176, 6, 101, 10, 61, 156, 235, 88, 136, 162, 191, 89, 50, 18, 19, 122, 61, 158, 161, 162, 48, 56, 0, 90, 234, 76, 149, 169, 82, 2, 17, 0, 0, 0, 3, 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