Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e8a80d6c774dd2468bcd80b9f1f77dce7e56d03f847de7fad1d0b69cb86cb52

Tx prefix hash: 9220114f14fedca4eb1c5e586d806fd1251fbe85c5ce1f082e57a85c33257317
Tx public key: 5fbc4ca68a27109404e0c300c410d5ed8612dcbc3f6da47ab4650ee9e599d2b8
Timestamp: 1582972969 Timestamp [UCT]: 2020-02-29 10:42:49 Age [y:d:h:m:s]: 04:277:12:07:34
Block: 73945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1092066 RingCT/type: yes/0
Extra: 015fbc4ca68a27109404e0c300c410d5ed8612dcbc3f6da47ab4650ee9e599d2b8021100000176c71d3ff9000000000000000000

1 output(s) for total of 349.148001791000 dcy

stealth address amount amount idx
00: b86625a521704657c68c5c54dd4f073478cee66ee68bceba727e5ca4d3c47921 349.148001791000 136657 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": 73955, "vin": [ { "gen": { "height": 73945 } } ], "vout": [ { "amount": 349148001791, "target": { "key": "b86625a521704657c68c5c54dd4f073478cee66ee68bceba727e5ca4d3c47921" } } ], "extra": [ 1, 95, 188, 76, 166, 138, 39, 16, 148, 4, 224, 195, 0, 196, 16, 213, 237, 134, 18, 220, 188, 63, 109, 164, 122, 180, 101, 14, 233, 229, 153, 210, 184, 2, 17, 0, 0, 1, 118, 199, 29, 63, 249, 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