Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7130abb48526a8fd875030e4e8378adf843af8391692a67003ef3ceb83aa6275

Tx prefix hash: 34d5f335bfc65f44e563ae098cf8b421368ce9162bac4a9ddeb66b231952a5e8
Tx public key: 57a37919c0664adf1f27aa5a63f9efe9e7997440f1079c1de6cfdddc88d0b842
Timestamp: 1696233848 Timestamp [UCT]: 2023-10-02 08:04:08 Age [y:d:h:m:s]: 01:199:01:17:22
Block: 860727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403321 RingCT/type: yes/0
Extra: 0157a37919c0664adf1f27aa5a63f9efe9e7997440f1079c1de6cfdddc88d0b84202110000000875e3f0e9000000000000000000

1 output(s) for total of 0.863086225000 dcy

stealth address amount amount idx
00: 929515e2e182c96d8a1d1ff1f92860a2294a2428bba7e9d9b2e9bb5c522f4d13 0.863086225000 1315025 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": 860737, "vin": [ { "gen": { "height": 860727 } } ], "vout": [ { "amount": 863086225, "target": { "key": "929515e2e182c96d8a1d1ff1f92860a2294a2428bba7e9d9b2e9bb5c522f4d13" } } ], "extra": [ 1, 87, 163, 121, 25, 192, 102, 74, 223, 31, 39, 170, 90, 99, 249, 239, 233, 231, 153, 116, 64, 241, 7, 156, 29, 230, 207, 221, 220, 136, 208, 184, 66, 2, 17, 0, 0, 0, 8, 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