Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5881eab96aad9eda93ec4ba8cce2e55b146b5d1993bdd93b1371c4b7f510a8bb

Tx prefix hash: e3fabe79b255d32e928fdb8585d34c9bd00731d8a0a18b4ca0bbac5f940fd287
Tx public key: 8ccecf9dd0e877cb6921fb5ba354d7c2550da5604bd63225acdee058a45b27e2
Timestamp: 1578655095 Timestamp [UCT]: 2020-01-10 11:18:15 Age [y:d:h:m:s]: 04:352:10:13:21
Block: 42567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141280 RingCT/type: yes/0
Extra: 018ccecf9dd0e877cb6921fb5ba354d7c2550da5604bd63225acdee058a45b27e202110000009cbd0f9f9f000000000000000000

1 output(s) for total of 443.566462714000 dcy

stealth address amount amount idx
00: ec40ee4cde375493aeca17173d9604d53d9886e78610bfcabfc096378e174226 443.566462714000 76741 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": 42577, "vin": [ { "gen": { "height": 42567 } } ], "vout": [ { "amount": 443566462714, "target": { "key": "ec40ee4cde375493aeca17173d9604d53d9886e78610bfcabfc096378e174226" } } ], "extra": [ 1, 140, 206, 207, 157, 208, 232, 119, 203, 105, 33, 251, 91, 163, 84, 215, 194, 85, 13, 165, 96, 75, 214, 50, 37, 172, 222, 224, 88, 164, 91, 39, 226, 2, 17, 0, 0, 0, 156, 189, 15, 159, 159, 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