Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08730c1786d893e1c4c0e33a9cc02c302364877fc2b76de63961f8f8af7fa5a3

Tx prefix hash: cf609e778ae4f1578e7110d27846f42b7be51ce2e4b94a438090025091bb2b3a
Tx public key: 11a897a79ce0fcf041de3c9cd08169632eb1ecb88e6c0ef72161297d80d1de96
Timestamp: 1574751742 Timestamp [UCT]: 2019-11-26 07:02:22 Age [y:d:h:m:s]: 05:169:15:54:16
Block: 17711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1263904 RingCT/type: yes/0
Extra: 0111a897a79ce0fcf041de3c9cd08169632eb1ecb88e6c0ef72161297d80d1de960211000000025d286194000000000000000000

1 output(s) for total of 536.187870172000 dcy

stealth address amount amount idx
00: 1c214d24253ea2ef08f543fd60afc4a0512d493e065790fa9ef351d296722551 536.187870172000 26149 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": 17721, "vin": [ { "gen": { "height": 17711 } } ], "vout": [ { "amount": 536187870172, "target": { "key": "1c214d24253ea2ef08f543fd60afc4a0512d493e065790fa9ef351d296722551" } } ], "extra": [ 1, 17, 168, 151, 167, 156, 224, 252, 240, 65, 222, 60, 156, 208, 129, 105, 99, 46, 177, 236, 184, 142, 108, 14, 247, 33, 97, 41, 125, 128, 209, 222, 150, 2, 17, 0, 0, 0, 2, 93, 40, 97, 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