Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b757753ed87038cdd7ce88be66dc4b31bc7de4d9aa6b849b94efa87b648132e9

Tx prefix hash: 4a4604219260f1f2d80f7f6dd8f21b0992281a1cd6e6565b33d258b6d3cea1c2
Tx public key: 0ab326986e3a9eff1903ccbc818e45f56161287c2ac30608f588e00beabed1d5
Timestamp: 1733945156 Timestamp [UCT]: 2024-12-11 19:25:56 Age [y:d:h:m:s]: 00:189:04:18:17
Block: 1173081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134893 RingCT/type: yes/0
Extra: 010ab326986e3a9eff1903ccbc818e45f56161287c2ac30608f588e00beabed1d5021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6e05d0fd20bf72eb267f3e56fd683c6f356bed2c5c42845c2051a9a5139a01b 0.600000000000 1659060 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": 1173091, "vin": [ { "gen": { "height": 1173081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6e05d0fd20bf72eb267f3e56fd683c6f356bed2c5c42845c2051a9a5139a01b" } } ], "extra": [ 1, 10, 179, 38, 152, 110, 58, 158, 255, 25, 3, 204, 188, 129, 142, 69, 245, 97, 97, 40, 124, 42, 195, 6, 8, 245, 136, 224, 11, 234, 190, 209, 213, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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