Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e667f19ff5535eaba3f50ed39aca210551dff62ec1c5759015c66f8ddbf65d9

Tx prefix hash: 79ddb2431c85013d3d9c5b1b84758150a18c2730b607ae8a06a41c98742bdaf6
Tx public key: 990eb4111f5322f568852e10779d376cdf0963d3ffca181c881d9d26acf5033f
Timestamp: 1578825422 Timestamp [UCT]: 2020-01-12 10:37:02 Age [y:d:h:m:s]: 05:096:12:07:47
Block: 43878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1219131 RingCT/type: yes/0
Extra: 01990eb4111f5322f568852e10779d376cdf0963d3ffca181c881d9d26acf5033f0211000000084ac5aa02000000000000000000

1 output(s) for total of 439.151947779000 dcy

stealth address amount amount idx
00: 51f076a123eece3b630bdc15905e3e6bea7f76fd4cbbfb33c38f20fd5d72cf56 439.151947779000 79625 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": 43888, "vin": [ { "gen": { "height": 43878 } } ], "vout": [ { "amount": 439151947779, "target": { "key": "51f076a123eece3b630bdc15905e3e6bea7f76fd4cbbfb33c38f20fd5d72cf56" } } ], "extra": [ 1, 153, 14, 180, 17, 31, 83, 34, 245, 104, 133, 46, 16, 119, 157, 55, 108, 223, 9, 99, 211, 255, 202, 24, 28, 136, 29, 157, 38, 172, 245, 3, 63, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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