Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 750f740bd0563edf602ad67f0ad07aa3ce8c2e25c2f1401ef6b9dec222f95518

Tx prefix hash: 609c301087c060d17300e7338522f39b2c2f9b2ab978c5c73277fb29213efd24
Tx public key: 759932d7161e3d9129dbb43d01b990eeeedb4d40f0daa7aea12fef98b55dd941
Timestamp: 1710458171 Timestamp [UCT]: 2024-03-14 23:16:11 Age [y:d:h:m:s]: 00:347:13:01:46
Block: 978469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248453 RingCT/type: yes/0
Extra: 01759932d7161e3d9129dbb43d01b990eeeedb4d40f0daa7aea12fef98b55dd9410211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 156d39616f17fb181eaa1537a2ccce0dc3704f2a7cde25105c4a049548e0f443 0.600000000000 1438496 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": 978479, "vin": [ { "gen": { "height": 978469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "156d39616f17fb181eaa1537a2ccce0dc3704f2a7cde25105c4a049548e0f443" } } ], "extra": [ 1, 117, 153, 50, 215, 22, 30, 61, 145, 41, 219, 180, 61, 1, 185, 144, 238, 238, 219, 77, 64, 240, 218, 167, 174, 161, 47, 239, 152, 181, 93, 217, 65, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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