Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 660b84c2f6da8a660dd405913a3396bc8c04cdd7be35cde2dba2298660c1b16d

Tx prefix hash: f185c67bb45947ebbe39925be0dcfc51d88829f8214ec1b56f371e59f9e09de5
Tx public key: 1126d3ef1fe39bb4ffbcd6aa54f2ba1f2d345a77c4e061b6bccd4d6c76d03510
Timestamp: 1684576094 Timestamp [UCT]: 2023-05-20 09:48:14 Age [y:d:h:m:s]: 02:008:11:55:30
Block: 764129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528190 RingCT/type: yes/0
Extra: 011126d3ef1fe39bb4ffbcd6aa54f2ba1f2d345a77c4e061b6bccd4d6c76d03510021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.803530954000 dcy

stealth address amount amount idx
00: c432cc93c0e8bfde5667f61c6b2ca9f341833bee810eefd1485d71aa2981b984 1.803530954000 1213024 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": 764139, "vin": [ { "gen": { "height": 764129 } } ], "vout": [ { "amount": 1803530954, "target": { "key": "c432cc93c0e8bfde5667f61c6b2ca9f341833bee810eefd1485d71aa2981b984" } } ], "extra": [ 1, 17, 38, 211, 239, 31, 227, 155, 180, 255, 188, 214, 170, 84, 242, 186, 31, 45, 52, 90, 119, 196, 224, 97, 182, 188, 205, 77, 108, 118, 208, 53, 16, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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