Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 429d91cf3252df0b5f93d9c0a47cf13d6fe366ad46235335c09e2435e2178dce

Tx prefix hash: 50a3cc9051d72a0c998032e19deaa0bddfd0bc4750d9251fe0fea9c3dc4fc896
Tx public key: 4f922db408911f1b822c1fada34f67778e788982ea8ba768aa82be00285bb779
Timestamp: 1574708566 Timestamp [UCT]: 2019-11-25 19:02:46 Age [y:d:h:m:s]: 04:346:17:29:01
Block: 17351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129726 RingCT/type: yes/0
Extra: 014f922db408911f1b822c1fada34f67778e788982ea8ba768aa82be00285bb779021100000001f95225a5000000000000000000

1 output(s) for total of 537.662584051000 dcy

stealth address amount amount idx
00: 6954e6ed54824f8ca461de2761d2cafb8729e5afd5aec16dff6ec270352caa0d 537.662584051000 25103 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": 17361, "vin": [ { "gen": { "height": 17351 } } ], "vout": [ { "amount": 537662584051, "target": { "key": "6954e6ed54824f8ca461de2761d2cafb8729e5afd5aec16dff6ec270352caa0d" } } ], "extra": [ 1, 79, 146, 45, 180, 8, 145, 31, 27, 130, 44, 31, 173, 163, 79, 103, 119, 142, 120, 137, 130, 234, 139, 167, 104, 170, 130, 190, 0, 40, 91, 183, 121, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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