Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69a8961a01ac1b3615d6fb21f32dafc92b337a79fb3018d282ac5e468ed91058

Tx prefix hash: c9b24d32f8cc5aef6eb1348515c90632be8099b54367fdc3699e25152af7655f
Tx public key: c0a8233db39af971c17ceb24e930628b4b34efc2302a44e4a420fb9e71734c1a
Timestamp: 1719486808 Timestamp [UCT]: 2024-06-27 11:13:28 Age [y:d:h:m:s]: 01:134:01:49:47
Block: 1053298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354370 RingCT/type: yes/0
Extra: 01c0a8233db39af971c17ceb24e930628b4b34efc2302a44e4a420fb9e71734c1a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6849a27d41421cc0c6b2b88ca0427c82dac7d68bedbff2774c610b1c466b09f6 0.600000000000 1523645 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": 1053308, "vin": [ { "gen": { "height": 1053298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6849a27d41421cc0c6b2b88ca0427c82dac7d68bedbff2774c610b1c466b09f6" } } ], "extra": [ 1, 192, 168, 35, 61, 179, 154, 249, 113, 193, 124, 235, 36, 233, 48, 98, 139, 75, 52, 239, 194, 48, 42, 68, 228, 164, 32, 251, 158, 113, 115, 76, 26, 2, 17, 0, 0, 0, 2, 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