Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c7efd07680ff94aecf5909858291028fb5fed08e9908e35caffa65b28518797

Tx prefix hash: 6d6dffffbb1aaf7bf09957f4c964d3f9745ac77cc727b8d6d395068b98d168df
Tx public key: b7b6b9802cbed464e5465b2bf88733e5f092546677da59d86acd2ca779b1d526
Timestamp: 1700125260 Timestamp [UCT]: 2023-11-16 09:01:00 Age [y:d:h:m:s]: 01:357:17:41:27
Block: 892792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514566 RingCT/type: yes/0
Extra: 01b7b6b9802cbed464e5465b2bf88733e5f092546677da59d86acd2ca779b1d52602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.675786454000 dcy

stealth address amount amount idx
00: 46fb0c0bd3d5daa38c6552fa4546dd1b373293d20982c91ab2d08a8a147a81a5 0.675786454000 1348923 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": 892802, "vin": [ { "gen": { "height": 892792 } } ], "vout": [ { "amount": 675786454, "target": { "key": "46fb0c0bd3d5daa38c6552fa4546dd1b373293d20982c91ab2d08a8a147a81a5" } } ], "extra": [ 1, 183, 182, 185, 128, 44, 190, 212, 100, 229, 70, 91, 43, 248, 135, 51, 229, 240, 146, 84, 102, 119, 218, 89, 216, 106, 205, 44, 167, 121, 177, 213, 38, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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