Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3cb4533f086b843f915e1fe0ececb7513d27ce830ee56603e7e8bfa03baf79f

Tx prefix hash: 20645b3cea19070dd9b718e2355ba7c1d441162b37ca1a2430360575314c9880
Tx public key: d1611bf8c962d31fe4c6af0a4035fa73e9a53d57318ced8f4fce5df4786f36bf
Timestamp: 1674309351 Timestamp [UCT]: 2023-01-21 13:55:51 Age [y:d:h:m:s]: 02:094:23:20:49
Block: 679624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 589544 RingCT/type: yes/0
Extra: 01d1611bf8c962d31fe4c6af0a4035fa73e9a53d57318ced8f4fce5df4786f36bf0211000000025029cbac000000000000000000

1 output(s) for total of 3.436556637000 dcy

stealth address amount amount idx
00: 4e5004c06d2a87a1186bd9ee54ba27ff71465e82278fc51c17b5a0bd2d4dc09b 3.436556637000 1121629 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": 679634, "vin": [ { "gen": { "height": 679624 } } ], "vout": [ { "amount": 3436556637, "target": { "key": "4e5004c06d2a87a1186bd9ee54ba27ff71465e82278fc51c17b5a0bd2d4dc09b" } } ], "extra": [ 1, 209, 97, 27, 248, 201, 98, 211, 31, 228, 198, 175, 10, 64, 53, 250, 115, 233, 165, 61, 87, 49, 140, 237, 143, 79, 206, 93, 244, 120, 111, 54, 191, 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