Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96eb168146b7dfa715900952769ca252ed0cbf6d0a34c1e4cd7d3c6faa7bc67b

Tx prefix hash: 3b7529721827e78a769c3fe58e2e22d72f0394508fc0cbc8516391dd1f169dc8
Tx public key: 35baf93671aa218e10a4110bada9e294214a2db904db5bf0c81365e674fa4434
Timestamp: 1681384211 Timestamp [UCT]: 2023-04-13 11:10:11 Age [y:d:h:m:s]: 02:066:19:41:39
Block: 737636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569851 RingCT/type: yes/0
Extra: 0135baf93671aa218e10a4110bada9e294214a2db904db5bf0c81365e674fa44340211000000015029cbac000000000000000000

1 output(s) for total of 2.207526603000 dcy

stealth address amount amount idx
00: a3c482729a4c1409c2b2e79a0ca8fd578c03781ee75b812e917b9b6ff853568c 2.207526603000 1184225 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": 737646, "vin": [ { "gen": { "height": 737636 } } ], "vout": [ { "amount": 2207526603, "target": { "key": "a3c482729a4c1409c2b2e79a0ca8fd578c03781ee75b812e917b9b6ff853568c" } } ], "extra": [ 1, 53, 186, 249, 54, 113, 170, 33, 142, 16, 164, 17, 11, 173, 169, 226, 148, 33, 74, 45, 185, 4, 219, 91, 240, 200, 19, 101, 230, 116, 250, 68, 52, 2, 17, 0, 0, 0, 1, 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