Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1285603bcf686e7d32fd75db987a12c3a8b93c9bf3e8c6397200d11a175906e8

Tx prefix hash: dd017e39cb5b46cb6ff873b3056b01e43ffb844c3441aff6dc4a75f2900d7a7e
Tx public key: 56c4808f234a24ad796abdeec2768239b8605295c3b72d26a6a0435877576a52
Timestamp: 1672231800 Timestamp [UCT]: 2022-12-28 12:50:00 Age [y:d:h:m:s]: 02:103:01:57:45
Block: 662381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 595387 RingCT/type: yes/0
Extra: 0156c4808f234a24ad796abdeec2768239b8605295c3b72d26a6a0435877576a52021100000001faf35c9c000000000000000000

1 output(s) for total of 3.919735371000 dcy

stealth address amount amount idx
00: d464a31549e7efaee573328fe715969d15a4a4372ea4817c9b80697e028e064f 3.919735371000 1103222 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": 662391, "vin": [ { "gen": { "height": 662381 } } ], "vout": [ { "amount": 3919735371, "target": { "key": "d464a31549e7efaee573328fe715969d15a4a4372ea4817c9b80697e028e064f" } } ], "extra": [ 1, 86, 196, 128, 143, 35, 74, 36, 173, 121, 106, 189, 238, 194, 118, 130, 57, 184, 96, 82, 149, 195, 183, 45, 38, 166, 160, 67, 88, 119, 87, 106, 82, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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