Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f84045018fbbcae1e9e1d83f66fa3ef0c2b73c595fff65fb5be8de66a05e7fb

Tx prefix hash: 3938c0cad9ea158ac4a3d0ea14ababee8c26b832ea04aa56c36f5fd14463f7f1
Tx public key: b42e0dca7760a6768c25f17009311ae890f9edd0465ad4aedbbdd5a4e277fb0d
Timestamp: 1663121976 Timestamp [UCT]: 2022-09-14 02:19:36 Age [y:d:h:m:s]: 02:154:22:36:09
Block: 587464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 631993 RingCT/type: yes/0
Extra: 01b42e0dca7760a6768c25f17009311ae890f9edd0465ad4aedbbdd5a4e277fb0d021100000006143619d6000000000000000000

1 output(s) for total of 6.942053838000 dcy

stealth address amount amount idx
00: c3562e726352f273c672b569d03fbcbfa0a059f433615baa064c7fa9d2e4976f 6.942053838000 1021651 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": 587474, "vin": [ { "gen": { "height": 587464 } } ], "vout": [ { "amount": 6942053838, "target": { "key": "c3562e726352f273c672b569d03fbcbfa0a059f433615baa064c7fa9d2e4976f" } } ], "extra": [ 1, 180, 46, 13, 202, 119, 96, 166, 118, 140, 37, 241, 112, 9, 49, 26, 232, 144, 249, 237, 208, 70, 90, 212, 174, 219, 189, 213, 164, 226, 119, 251, 13, 2, 17, 0, 0, 0, 6, 20, 54, 25, 214, 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