Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7337af6cc0d31880b8bd2c8a12b707e58172fd1c19364a9cadb13c37d043e305

Tx prefix hash: 6648cd5df6329f790b3ebc91d975817840858464179d2662418f564d75e75683
Tx public key: f916b8e970618e4e6ac5644877bc9c283fd9f606435a056d6ef66b79e60accc3
Timestamp: 1679799936 Timestamp [UCT]: 2023-03-26 03:05:36 Age [y:d:h:m:s]: 02:015:19:08:26
Block: 725179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532808 RingCT/type: yes/0
Extra: 01f916b8e970618e4e6ac5644877bc9c283fd9f606435a056d6ef66b79e60accc30211000000025029cbac000000000000000000

1 output(s) for total of 2.427620595000 dcy

stealth address amount amount idx
00: a16c997bd35a8f5e1e8a1275b83d1467bf3e137f193e7872ba7c9436b9d95cbe 2.427620595000 1170270 of 0

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": 725189, "vin": [ { "gen": { "height": 725179 } } ], "vout": [ { "amount": 2427620595, "target": { "key": "a16c997bd35a8f5e1e8a1275b83d1467bf3e137f193e7872ba7c9436b9d95cbe" } } ], "extra": [ 1, 249, 22, 184, 233, 112, 97, 142, 78, 106, 197, 100, 72, 119, 188, 156, 40, 63, 217, 246, 6, 67, 90, 5, 109, 110, 246, 107, 121, 230, 10, 204, 195, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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