Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985f0031a935c706a373675af4658e8ee41aa4c9c7d411d84516dabc94a3519e

Tx prefix hash: 225360d5d57a8755f07e034e3c09336a754028d5e317d670f5a26e7feb39615c
Tx public key: 1e3a96d3a0c96161089f142417e1eda5ea7b0f24923fc4f70c45488891a5cd48
Timestamp: 1576424487 Timestamp [UCT]: 2019-12-15 15:41:27 Age [y:d:h:m:s]: 05:148:19:16:01
Block: 27383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1253159 RingCT/type: yes/0
Extra: 011e3a96d3a0c96161089f142417e1eda5ea7b0f24923fc4f70c45488891a5cd48021100000054ad433a0b000000000000000000

1 output(s) for total of 498.046187424000 dcy

stealth address amount amount idx
00: e75cb56300d8bec16de31fa58b536c855d3874bd74660ce5a2a8d4d077c42214 498.046187424000 45379 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": 27393, "vin": [ { "gen": { "height": 27383 } } ], "vout": [ { "amount": 498046187424, "target": { "key": "e75cb56300d8bec16de31fa58b536c855d3874bd74660ce5a2a8d4d077c42214" } } ], "extra": [ 1, 30, 58, 150, 211, 160, 201, 97, 97, 8, 159, 20, 36, 23, 225, 237, 165, 234, 123, 15, 36, 146, 63, 196, 247, 12, 69, 72, 136, 145, 165, 205, 72, 2, 17, 0, 0, 0, 84, 173, 67, 58, 11, 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