Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88d2714bb5e39b48addbefe26263cbd620291b48ea60fb44c1d7b81624368143

Tx prefix hash: edb5538d9ebb9ae0516b8d02dc2ff4d00949646698bae68c49771d3b14c558f1
Tx public key: 05518fa35b5598db2346ecb1ea3b11bfb5980f623a645eaed31bf1ed12f0fa00
Timestamp: 1704194610 Timestamp [UCT]: 2024-01-02 11:23:30 Age [y:d:h:m:s]: 01:016:15:21:27
Block: 926508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273228 RingCT/type: yes/0
Extra: 0105518fa35b5598db2346ecb1ea3b11bfb5980f623a645eaed31bf1ed12f0fa000211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f65a88d424379c48970a60d0d1c38135943aaa0ed410a507fb6dbd97a1d11e45 0.600000000000 1384294 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": 926518, "vin": [ { "gen": { "height": 926508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f65a88d424379c48970a60d0d1c38135943aaa0ed410a507fb6dbd97a1d11e45" } } ], "extra": [ 1, 5, 81, 143, 163, 91, 85, 152, 219, 35, 70, 236, 177, 234, 59, 17, 191, 181, 152, 15, 98, 58, 100, 94, 174, 211, 27, 241, 237, 18, 240, 250, 0, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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