Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e783f876b3f1edb23ceee89ccb8995e6ec97736eeba8bb44cfb2f8325a28adb

Tx prefix hash: 6ed16427f805c0221d6c3576c1ce795a781e6356d970ef4ddd2b1a5626bf3634
Tx public key: 5de0ed49fc7c4fe227e1dd0ef681e5c5a2a7c131560e6227d8f35b34b5e39b64
Timestamp: 1710443862 Timestamp [UCT]: 2024-03-14 19:17:42 Age [y:d:h:m:s]: 01:263:21:51:27
Block: 978349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447343 RingCT/type: yes/0
Extra: 015de0ed49fc7c4fe227e1dd0ef681e5c5a2a7c131560e6227d8f35b34b5e39b6402110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2bb41967b2d6c8c3e1fbf7d17f45238e5fffe4e27be0dc07f675b8fc42da9b6 0.600000000000 1438372 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": 978359, "vin": [ { "gen": { "height": 978349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2bb41967b2d6c8c3e1fbf7d17f45238e5fffe4e27be0dc07f675b8fc42da9b6" } } ], "extra": [ 1, 93, 224, 237, 73, 252, 124, 79, 226, 39, 225, 221, 14, 246, 129, 229, 197, 162, 167, 193, 49, 86, 14, 98, 39, 216, 243, 91, 52, 181, 227, 155, 100, 2, 17, 0, 0, 0, 14, 82, 212, 126, 148, 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