Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2990663827a4b24d9c5e8a16b2b21704ac0c03f17b384e73fdfc9efaf0204d05

Tx prefix hash: 3395b259fe9a707a3be7efc2f9cbaacc03cec9bc9a1f8b64076c6a2c11d7e4b7
Tx public key: 5edd6b94165ab16c9fa79a2856e96bc5d51db84610eb46afaafce77319fd1a64
Timestamp: 1735446001 Timestamp [UCT]: 2024-12-29 04:20:01 Age [y:d:h:m:s]: 00:170:20:37:55
Block: 1185478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121826 RingCT/type: yes/0
Extra: 015edd6b94165ab16c9fa79a2856e96bc5d51db84610eb46afaafce77319fd1a640211000000111f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c036b37c5145e9221fed5e7d8e8ee93575bdeefa23d52852ba659cce120d8597 0.600000000000 1671949 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": 1185488, "vin": [ { "gen": { "height": 1185478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c036b37c5145e9221fed5e7d8e8ee93575bdeefa23d52852ba659cce120d8597" } } ], "extra": [ 1, 94, 221, 107, 148, 22, 90, 177, 108, 159, 167, 154, 40, 86, 233, 107, 197, 213, 29, 184, 70, 16, 235, 70, 175, 170, 252, 231, 115, 25, 253, 26, 100, 2, 17, 0, 0, 0, 17, 31, 10, 83, 235, 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