Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 793d812a8910bb8257452ad81cdd907a505342eb5365ee48241eb67e1a072bd1

Tx prefix hash: 4dbc27f22e0fbdaa10f23e08f01df300a979cc5b95c0b301775aac5d5623ec0b
Tx public key: 69ed8f1a8552d60036eb3386afe4a3edb37e51de73840dacfa3f8a4526ca25e8
Timestamp: 1580569113 Timestamp [UCT]: 2020-02-01 14:58:33 Age [y:d:h:m:s]: 04:332:04:54:59
Block: 56578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128646 RingCT/type: yes/0
Extra: 0169ed8f1a8552d60036eb3386afe4a3edb37e51de73840dacfa3f8a4526ca25e80211000000012264afe6000000000000000000

1 output(s) for total of 398.597364365000 dcy

stealth address amount amount idx
00: 7a26ef3e5f56877a3c2ccd589fad7fe156afe1a44db3f8565f73540f45d5560c 398.597364365000 104337 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": 56588, "vin": [ { "gen": { "height": 56578 } } ], "vout": [ { "amount": 398597364365, "target": { "key": "7a26ef3e5f56877a3c2ccd589fad7fe156afe1a44db3f8565f73540f45d5560c" } } ], "extra": [ 1, 105, 237, 143, 26, 133, 82, 214, 0, 54, 235, 51, 134, 175, 228, 163, 237, 179, 126, 81, 222, 115, 132, 13, 172, 250, 63, 138, 69, 38, 202, 37, 232, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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