Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68eca17519b45defa98e4249fb7580811e789703bbe450cdd9a5d53c8801bc42

Tx prefix hash: bbf5a0200dd32cca25e6181ec8df29bd3f834abd0256c2543b8208d5fa0a32fe
Tx public key: 0fe6692ac9b5d6d456526fb4a704df527a77fa68f1fed983e299d608937d3329
Timestamp: 1707648382 Timestamp [UCT]: 2024-02-11 10:46:22 Age [y:d:h:m:s]: 01:067:08:17:16
Block: 955147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309193 RingCT/type: yes/0
Extra: 010fe6692ac9b5d6d456526fb4a704df527a77fa68f1fed983e299d608937d3329021100000004b6e2dc33000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d483f04a18bd5deac912d9f2cbc9fb935ba3443d9a1494a7ef2f632794d6809 0.600000000000 1414433 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": 955157, "vin": [ { "gen": { "height": 955147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d483f04a18bd5deac912d9f2cbc9fb935ba3443d9a1494a7ef2f632794d6809" } } ], "extra": [ 1, 15, 230, 105, 42, 201, 181, 214, 212, 86, 82, 111, 180, 167, 4, 223, 82, 122, 119, 250, 104, 241, 254, 217, 131, 226, 153, 214, 8, 147, 125, 51, 41, 2, 17, 0, 0, 0, 4, 182, 226, 220, 51, 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