Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 074f9f0010277823b1cdafbe26d9f41c4701985cc16d53f9c7147e0dcbce2fbd

Tx prefix hash: d5e24cc06e03ec4180b78e1e67e82cf34d6dbc5c3848ee9b08d8fd3f019d7b06
Tx public key: 0210c4f743d090826ea4d31da1017c365887c9427b7a2c096444643845880bad
Timestamp: 1617106080 Timestamp [UCT]: 2021-03-30 12:08:00 Age [y:d:h:m:s]: 03:232:03:58:19
Block: 229688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 925370 RingCT/type: yes/0
Extra: 010210c4f743d090826ea4d31da1017c365887c9427b7a2c096444643845880bad0211000000534405d762000000000000000000

1 output(s) for total of 106.401779187000 dcy

stealth address amount amount idx
00: 79d3f80773f93210af418714b2182ae4875cf4b8ecaf8e66f44d924ce97b8e06 106.401779187000 476668 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": 229698, "vin": [ { "gen": { "height": 229688 } } ], "vout": [ { "amount": 106401779187, "target": { "key": "79d3f80773f93210af418714b2182ae4875cf4b8ecaf8e66f44d924ce97b8e06" } } ], "extra": [ 1, 2, 16, 196, 247, 67, 208, 144, 130, 110, 164, 211, 29, 161, 1, 124, 54, 88, 135, 201, 66, 123, 122, 44, 9, 100, 68, 100, 56, 69, 136, 11, 173, 2, 17, 0, 0, 0, 83, 68, 5, 215, 98, 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