Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea08cde6e831496020479e040afe10cc505a63f27a4902b0e1ecf4591123b3f

Tx prefix hash: ea7b7f6b0c2581c1c62792f603e2ff6bd26631f60044ab251ca7460a321df39c
Tx public key: 02e1cd52001d7509db58902c1c4ca9271237085ff5d150e8dfdcc99e46aa91b5
Timestamp: 1722285914 Timestamp [UCT]: 2024-07-29 20:45:14 Age [y:d:h:m:s]: 00:273:16:15:15
Block: 1076502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195531 RingCT/type: yes/0
Extra: 0102e1cd52001d7509db58902c1c4ca9271237085ff5d150e8dfdcc99e46aa91b502110000001ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9216a15b4ef941738687d7b0cb4a13bdb35c27f8de54faf4a010a797d1485880 0.600000000000 1549039 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": 1076512, "vin": [ { "gen": { "height": 1076502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9216a15b4ef941738687d7b0cb4a13bdb35c27f8de54faf4a010a797d1485880" } } ], "extra": [ 1, 2, 225, 205, 82, 0, 29, 117, 9, 219, 88, 144, 44, 28, 76, 169, 39, 18, 55, 8, 95, 245, 209, 80, 232, 223, 220, 201, 158, 70, 170, 145, 181, 2, 17, 0, 0, 0, 26, 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