Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76e9f39b719ee5dbb4f9a4c87331d32fc424b141983c382ed21c1a7248710df8

Tx prefix hash: 0087a587489f995605fc563d769c9978b1263b8cde1d65fd5f88739b6f2296a8
Tx public key: 0453cb5ceda925095ede2ab92eefa672ba021fef40412081d277a14941c8f3bf
Timestamp: 1580370463 Timestamp [UCT]: 2020-01-30 07:47:43 Age [y:d:h:m:s]: 05:101:18:08:30
Block: 54972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1224589 RingCT/type: yes/0
Extra: 010453cb5ceda925095ede2ab92eefa672ba021fef40412081d277a14941c8f3bf021100000002ff58ae94000000000000000000

1 output(s) for total of 403.511363597000 dcy

stealth address amount amount idx
00: c5e7c3a41e924409b55f1df7c6b89bf292b2427253c6bac95622e9e65c31c578 403.511363597000 101638 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": 54982, "vin": [ { "gen": { "height": 54972 } } ], "vout": [ { "amount": 403511363597, "target": { "key": "c5e7c3a41e924409b55f1df7c6b89bf292b2427253c6bac95622e9e65c31c578" } } ], "extra": [ 1, 4, 83, 203, 92, 237, 169, 37, 9, 94, 222, 42, 185, 46, 239, 166, 114, 186, 2, 31, 239, 64, 65, 32, 129, 210, 119, 161, 73, 65, 200, 243, 191, 2, 17, 0, 0, 0, 2, 255, 88, 174, 148, 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