Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec27575f23d23f5631a9789b5624aff2f8209df0a884b38f9ad7f8e927d8acea

Tx prefix hash: c1de0d5e3edfb3f02e93a6dd92099c4a43e6f37d16edfaa932178ec685e8dd76
Tx public key: 093500a246bcd837c9623ea771d30e406c6529266bc7417ebb63731ca6edc02f
Timestamp: 1577798788 Timestamp [UCT]: 2019-12-31 13:26:28 Age [y:d:h:m:s]: 05:102:20:07:46
Block: 35779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1223268 RingCT/type: yes/0
Extra: 01093500a246bcd837c9623ea771d30e406c6529266bc7417ebb63731ca6edc02f0211000000088a2ee0d9000000000000000000

1 output(s) for total of 467.143353659000 dcy

stealth address amount amount idx
00: ab1da6953aebf9dc4c9b9ef940423f954b292c4b68931252d9c0c65d072fcfc2 467.143353659000 60409 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": 35789, "vin": [ { "gen": { "height": 35779 } } ], "vout": [ { "amount": 467143353659, "target": { "key": "ab1da6953aebf9dc4c9b9ef940423f954b292c4b68931252d9c0c65d072fcfc2" } } ], "extra": [ 1, 9, 53, 0, 162, 70, 188, 216, 55, 201, 98, 62, 167, 113, 211, 14, 64, 108, 101, 41, 38, 107, 199, 65, 126, 187, 99, 115, 28, 166, 237, 192, 47, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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