Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89216a2a4caa097cbfd9c17dce6a9b2d7e6e8b56d39feb12f7ee8f5de4a6f006

Tx prefix hash: 12b0d28009da2408c0f4d26fee7730d01d41fd135f18a4b1215ac3f7077133d9
Tx public key: 7a251f753ed82a615932011f4cd0561f49f9c419dd8e1cc24e41dc94cc8688c8
Timestamp: 1710754813 Timestamp [UCT]: 2024-03-18 09:40:13 Age [y:d:h:m:s]: 01:315:12:52:29
Block: 980934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484112 RingCT/type: yes/0
Extra: 017a251f753ed82a615932011f4cd0561f49f9c419dd8e1cc24e41dc94cc8688c802110000001859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fea19e36464f82a815d3db0d70ec291ef1c62a3b9affa6612f3d36f6b0d5ed24 0.600000000000 1441019 of 15

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": 980944, "vin": [ { "gen": { "height": 980934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fea19e36464f82a815d3db0d70ec291ef1c62a3b9affa6612f3d36f6b0d5ed24" } } ], "extra": [ 1, 122, 37, 31, 117, 62, 216, 42, 97, 89, 50, 1, 31, 76, 208, 86, 31, 73, 249, 196, 25, 221, 142, 28, 194, 78, 65, 220, 148, 204, 134, 136, 200, 2, 17, 0, 0, 0, 24, 89, 218, 211, 245, 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