Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f187561838fdac5947872e10770fca1bfa3a0d36cd27d2cdaf5fd22e022d71

Tx prefix hash: 1d2f61878914e9b4880744f8b49878c5b069b48f3d1a4d7906bfcc9169bee70e
Tx public key: 3f988a488ac882e6ece1fe67b65e8089848b3783e1d3803f71e3eb827019e836
Timestamp: 1577165783 Timestamp [UCT]: 2019-12-24 05:36:23 Age [y:d:h:m:s]: 05:145:23:44:22
Block: 30401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1254266 RingCT/type: yes/0
Extra: 013f988a488ac882e6ece1fe67b65e8089848b3783e1d3803f71e3eb827019e836021100000001d81c26c0000000000000000000

1 output(s) for total of 486.709393978000 dcy

stealth address amount amount idx
00: a861f778a2c2473ee50c51c5d70f8c0954d41744bfce18bea7d64172c599b35a 486.709393978000 50205 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": 30411, "vin": [ { "gen": { "height": 30401 } } ], "vout": [ { "amount": 486709393978, "target": { "key": "a861f778a2c2473ee50c51c5d70f8c0954d41744bfce18bea7d64172c599b35a" } } ], "extra": [ 1, 63, 152, 138, 72, 138, 200, 130, 230, 236, 225, 254, 103, 182, 94, 128, 137, 132, 139, 55, 131, 225, 211, 128, 63, 113, 227, 235, 130, 112, 25, 232, 54, 2, 17, 0, 0, 0, 1, 216, 28, 38, 192, 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