Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd1d47f8b647fbf075c7883cc6a4081b0df5142dc771bd20d46649311ee0dfb

Tx prefix hash: b3792993de274995c108bedc53a1d8c7ebdf7900868b889c759beecadffe7b8a
Tx public key: cccf216e46d4cd35f2a09448f2b73875e0e1bcecef36b431130f8c4d2d44e98b
Timestamp: 1625420598 Timestamp [UCT]: 2021-07-04 17:43:18 Age [y:d:h:m:s]: 03:146:07:59:19
Block: 288260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 874249 RingCT/type: yes/0
Extra: 01cccf216e46d4cd35f2a09448f2b73875e0e1bcecef36b431130f8c4d2d44e98b02110000002d3525d189000000000000000000

1 output(s) for total of 68.057417457000 dcy

stealth address amount amount idx
00: 304095bcef76b4ca3ac572c0acf73bd9d0f48b2a7e8ce4a87da7b2a7d12775dc 68.057417457000 604001 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": 288270, "vin": [ { "gen": { "height": 288260 } } ], "vout": [ { "amount": 68057417457, "target": { "key": "304095bcef76b4ca3ac572c0acf73bd9d0f48b2a7e8ce4a87da7b2a7d12775dc" } } ], "extra": [ 1, 204, 207, 33, 110, 70, 212, 205, 53, 242, 160, 148, 72, 242, 183, 56, 117, 224, 225, 188, 236, 239, 54, 180, 49, 19, 15, 140, 77, 45, 68, 233, 139, 2, 17, 0, 0, 0, 45, 53, 37, 209, 137, 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