Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 588d9c7b5d6e7f8663eadbb8b7021aed511f935c0e04751832bfd2af2bf3d7ae

Tx prefix hash: ca0ce5e41dfec0628a7e3130bf7f72e92c4323868e5a3a229696ab35c34c3228
Tx public key: c0bad7c275a968e4a6b45f542076d4018e452acb3d7e1fdd0f762ae71c98191c
Timestamp: 1676323451 Timestamp [UCT]: 2023-02-13 21:24:11 Age [y:d:h:m:s]: 02:055:06:32:10
Block: 696348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561093 RingCT/type: yes/0
Extra: 01c0bad7c275a968e4a6b45f542076d4018e452acb3d7e1fdd0f762ae71c98191c0211000000015029cbac000000000000000000

1 output(s) for total of 3.024892373000 dcy

stealth address amount amount idx
00: d14a7e8a55b3e0c3631cec4d555904c1c2781dcd3f39f416039fa1de58222a3b 3.024892373000 1139335 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": 696358, "vin": [ { "gen": { "height": 696348 } } ], "vout": [ { "amount": 3024892373, "target": { "key": "d14a7e8a55b3e0c3631cec4d555904c1c2781dcd3f39f416039fa1de58222a3b" } } ], "extra": [ 1, 192, 186, 215, 194, 117, 169, 104, 228, 166, 180, 95, 84, 32, 118, 212, 1, 142, 69, 42, 203, 61, 126, 31, 221, 15, 118, 42, 231, 28, 152, 25, 28, 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