Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1860af4ed55881db4222c549c83a9bb941c262566facb0036301ad7120a85e7f

Tx prefix hash: fbc3f37f842b0ea452ba80c698e86f17595cf04a4bf225868ca9a442d2790e3c
Tx public key: d8a754f9a8f5c18e3eeeff917a09c33436389cb65c65d657b0c184eb569c1761
Timestamp: 1695720379 Timestamp [UCT]: 2023-09-26 09:26:19 Age [y:d:h:m:s]: 01:152:00:35:48
Block: 856467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369676 RingCT/type: yes/0
Extra: 01d8a754f9a8f5c18e3eeeff917a09c33436389cb65c65d657b0c184eb569c1761021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.891598522000 dcy

stealth address amount amount idx
00: 0db4ef70dfbdb29b1fcaf7d004074e6b2dff18b2ef80f3b8c0cf4428c44b54b0 0.891598522000 1310543 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": 856477, "vin": [ { "gen": { "height": 856467 } } ], "vout": [ { "amount": 891598522, "target": { "key": "0db4ef70dfbdb29b1fcaf7d004074e6b2dff18b2ef80f3b8c0cf4428c44b54b0" } } ], "extra": [ 1, 216, 167, 84, 249, 168, 245, 193, 142, 62, 238, 255, 145, 122, 9, 195, 52, 54, 56, 156, 182, 92, 101, 214, 87, 176, 193, 132, 235, 86, 156, 23, 97, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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