Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acaa9ca3f11123cb7d474a3f87c79f3fa15a732371f3228dbf21612c69c7bcd2

Tx prefix hash: f3d382fe06f1b980a3d171f624ef0e3fb12491efce510e769fef87e9e3fecb22
Tx public key: 114cc2f0b09db42e31e528bd3777191b1298aad69da7ef1e0fb08021b674bb6c
Timestamp: 1716624730 Timestamp [UCT]: 2024-05-25 08:12:10 Age [y:d:h:m:s]: 01:168:02:44:11
Block: 1029579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378741 RingCT/type: yes/0
Extra: 01114cc2f0b09db42e31e528bd3777191b1298aad69da7ef1e0fb08021b674bb6c02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 409a619b51f08b0ab849ed65f32643ce430fbe6482147bcbb8485fb449b7bda0 0.600000000000 1497710 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": 1029589, "vin": [ { "gen": { "height": 1029579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "409a619b51f08b0ab849ed65f32643ce430fbe6482147bcbb8485fb449b7bda0" } } ], "extra": [ 1, 17, 76, 194, 240, 176, 157, 180, 46, 49, 229, 40, 189, 55, 119, 25, 27, 18, 152, 170, 214, 157, 167, 239, 30, 15, 176, 128, 33, 182, 116, 187, 108, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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