Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b817293d330eac84627ff54b0bceb9b15d884c2fdd4fdaa0c25e05d910c8f68

Tx prefix hash: 27da94edbb2c136db77b2ede2f0371b60fa57e3d6ff55461890292d65e69bd1a
Tx public key: 277d79ec9ae2decfa63ff2291bcd5b5bcbb791560e4d39f2b848103872a5c826
Timestamp: 1707930431 Timestamp [UCT]: 2024-02-14 17:07:11 Age [y:d:h:m:s]: 00:333:11:59:44
Block: 957480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238752 RingCT/type: yes/0
Extra: 01277d79ec9ae2decfa63ff2291bcd5b5bcbb791560e4d39f2b848103872a5c8260211000000026d0f39ce000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cefec1b48175652c32340a5851b439ef1ef7e3dd39a961072d1ac6b5a5a70e8f 0.600000000000 1416798 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": 957490, "vin": [ { "gen": { "height": 957480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cefec1b48175652c32340a5851b439ef1ef7e3dd39a961072d1ac6b5a5a70e8f" } } ], "extra": [ 1, 39, 125, 121, 236, 154, 226, 222, 207, 166, 63, 242, 41, 27, 205, 91, 91, 203, 183, 145, 86, 14, 77, 57, 242, 184, 72, 16, 56, 114, 165, 200, 38, 2, 17, 0, 0, 0, 2, 109, 15, 57, 206, 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