Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf39217f8091220bc5699fc1c5d941915fc1565dc15568d0f83164017595336e

Tx prefix hash: de18c20be0e0518e8ca348474a55eeb561585e2a7c0e3e5e5c9636504c5614ff
Tx public key: a3d8596d7831662adb76d6d6c4978a2f38ed22106abb0580065539c8f5f5f4d7
Timestamp: 1582339766 Timestamp [UCT]: 2020-02-22 02:49:26 Age [y:d:h:m:s]: 04:311:22:17:11
Block: 69987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115392 RingCT/type: yes/0
Extra: 01a3d8596d7831662adb76d6d6c4978a2f38ed22106abb0580065539c8f5f5f4d7021100000013d81c26c0000000000000000000

1 output(s) for total of 359.836173406000 dcy

stealth address amount amount idx
00: 36c8d0dcc3f5cba28ab4df2ca37bf91898c94aed85e97d8cf4e795995a1392ce 359.836173406000 129143 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": 69997, "vin": [ { "gen": { "height": 69987 } } ], "vout": [ { "amount": 359836173406, "target": { "key": "36c8d0dcc3f5cba28ab4df2ca37bf91898c94aed85e97d8cf4e795995a1392ce" } } ], "extra": [ 1, 163, 216, 89, 109, 120, 49, 102, 42, 219, 118, 214, 214, 196, 151, 138, 47, 56, 237, 34, 16, 106, 187, 5, 128, 6, 85, 57, 200, 245, 245, 244, 215, 2, 17, 0, 0, 0, 19, 216, 28, 38, 192, 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