Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d12c44c9912542e027ecf06a597b521e28118f7bef39ff6ecf8dd9f1728f0ac

Tx prefix hash: aee6d5bbeb52fb0d917b03e0adf709ea29ed6edf7dba4867889c4596024f3196
Tx public key: f9aa64b81917c8bb1f30b6129d896600e998e6f1be10909c29a9c832c3b8b790
Timestamp: 1724446354 Timestamp [UCT]: 2024-08-23 20:52:34 Age [y:d:h:m:s]: 00:226:21:20:33
Block: 1094439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161988 RingCT/type: yes/0
Extra: 01f9aa64b81917c8bb1f30b6129d896600e998e6f1be10909c29a9c832c3b8b790021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44adaa76894eea18aaa2261fea16c7b6223607a83572011bac7ae24f1235a9b2 0.600000000000 1569556 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": 1094449, "vin": [ { "gen": { "height": 1094439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44adaa76894eea18aaa2261fea16c7b6223607a83572011bac7ae24f1235a9b2" } } ], "extra": [ 1, 249, 170, 100, 184, 25, 23, 200, 187, 31, 48, 182, 18, 157, 137, 102, 0, 233, 152, 230, 241, 190, 16, 144, 156, 41, 169, 200, 50, 195, 184, 183, 144, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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