Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd79cd47ef9086adc0a7614d415d6494dff5ae4ec0d5c063319fb4034f029c26

Tx prefix hash: 4fec57de5531a8f607da065225347f1d78a7c8c9b108e2a95ff436553d452895
Tx public key: 50feccd0d2578768788b810b4528666edab3b417542ca4f5ddf18fd2e047be2a
Timestamp: 1577994311 Timestamp [UCT]: 2020-01-02 19:45:11 Age [y:d:h:m:s]: 05:000:18:26:21
Block: 37401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150527 RingCT/type: yes/0
Extra: 0150feccd0d2578768788b810b4528666edab3b417542ca4f5ddf18fd2e047be2a021100000043d81c26c0000000000000000000

1 output(s) for total of 461.453101419000 dcy

stealth address amount amount idx
00: e93f80e183a25c8b8451b2900d3f1c6c7415670fe9cb4e21ef7a03feb2830ec1 461.453101419000 63465 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": 37411, "vin": [ { "gen": { "height": 37401 } } ], "vout": [ { "amount": 461453101419, "target": { "key": "e93f80e183a25c8b8451b2900d3f1c6c7415670fe9cb4e21ef7a03feb2830ec1" } } ], "extra": [ 1, 80, 254, 204, 208, 210, 87, 135, 104, 120, 139, 129, 11, 69, 40, 102, 110, 218, 179, 180, 23, 84, 44, 164, 245, 221, 241, 143, 210, 224, 71, 190, 42, 2, 17, 0, 0, 0, 67, 216, 28, 38, 192, 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