Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6323679fc8a2dd3fa5b305d6538130ee0141e7ec4700da55c7fec3d1ba84b6b

Tx prefix hash: 050200a4343508db5bb253c467009542492dd6a9aec0feefafc3f88a27992615
Tx public key: 10cc82eb2ad2d3cffb782804686ef03c63d9d40d550e9583a0fd893ff9413b2d
Timestamp: 1650129903 Timestamp [UCT]: 2022-04-16 17:25:03 Age [y:d:h:m:s]: 02:228:23:12:16
Block: 481549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 683561 RingCT/type: yes/0
Extra: 0110cc82eb2ad2d3cffb782804686ef03c63d9d40d550e9583a0fd893ff9413b2d02110000000375e3f0e9000000000000000000

1 output(s) for total of 15.575015769000 dcy

stealth address amount amount idx
00: e7193efb49ee2a6f2a1cbbdb5eb49db7be7148b5f333cf475b0dec04b846eedd 15.575015769000 902850 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": 481559, "vin": [ { "gen": { "height": 481549 } } ], "vout": [ { "amount": 15575015769, "target": { "key": "e7193efb49ee2a6f2a1cbbdb5eb49db7be7148b5f333cf475b0dec04b846eedd" } } ], "extra": [ 1, 16, 204, 130, 235, 42, 210, 211, 207, 251, 120, 40, 4, 104, 110, 240, 60, 99, 217, 212, 13, 85, 14, 149, 131, 160, 253, 137, 63, 249, 65, 59, 45, 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