Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d188d99f83e69db669b921f8dc641c81533c3b6f75ff7c67936b5ec081a60995

Tx prefix hash: a47aff1543cf18e2ad9f66cf5ae77292a52c12a8f3ad12667f7b9c29d180816f
Tx public key: 928745e37e890fbdd2c602024ac77bfe0b79eb7624edfbe3a9ec5d131dabcb46
Timestamp: 1687440843 Timestamp [UCT]: 2023-06-22 13:34:03 Age [y:d:h:m:s]: 01:211:23:09:36
Block: 787878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412839 RingCT/type: yes/0
Extra: 01928745e37e890fbdd2c602024ac77bfe0b79eb7624edfbe3a9ec5d131dabcb4602110000000375e3f0e9000000000000000000

1 output(s) for total of 1.504642310000 dcy

stealth address amount amount idx
00: a72b94e86c9ba479c0e11742d11e098e8117023f9e336ea895e96ab168e6c1f6 1.504642310000 1237963 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": 787888, "vin": [ { "gen": { "height": 787878 } } ], "vout": [ { "amount": 1504642310, "target": { "key": "a72b94e86c9ba479c0e11742d11e098e8117023f9e336ea895e96ab168e6c1f6" } } ], "extra": [ 1, 146, 135, 69, 227, 126, 137, 15, 189, 210, 198, 2, 2, 74, 199, 123, 254, 11, 121, 235, 118, 36, 237, 251, 227, 169, 236, 93, 19, 29, 171, 203, 70, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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