Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c118275fbba571c48e3e0e5fc5392a13278818054ccc13fa2cfbab38dd3ac08d

Tx prefix hash: ad72482e1af4455b0dc42d373f7aba6412c746d4501e0d794752c82fc277c129
Tx public key: 3fb34b88a5a9de3fbc35a8c0b83ccb31492c6b70f80f58b125031c0113a06876
Timestamp: 1685064696 Timestamp [UCT]: 2023-05-26 01:31:36 Age [y:d:h:m:s]: 01:238:07:39:07
Block: 768172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431759 RingCT/type: yes/0
Extra: 013fb34b88a5a9de3fbc35a8c0b83ccb31492c6b70f80f58b125031c0113a0687602110000000275e3f0e9000000000000000000

1 output(s) for total of 1.748748911000 dcy

stealth address amount amount idx
00: c5a888533b9f7041e6e65b75906ab5b2f671f5b53f1e5e28fa91602d85a52c0f 1.748748911000 1217363 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": 768182, "vin": [ { "gen": { "height": 768172 } } ], "vout": [ { "amount": 1748748911, "target": { "key": "c5a888533b9f7041e6e65b75906ab5b2f671f5b53f1e5e28fa91602d85a52c0f" } } ], "extra": [ 1, 63, 179, 75, 136, 165, 169, 222, 63, 188, 53, 168, 192, 184, 60, 203, 49, 73, 44, 107, 112, 248, 15, 88, 177, 37, 3, 28, 1, 19, 160, 104, 118, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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