Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a8d554eca8cd00701e0f5fc6520f2c471e36368a68a2aa3e391e9bba0918117

Tx prefix hash: cfd504a3818ab2f54bcc856df780c228446e0253067f126f8dcb788d81170406
Tx public key: d74144fdb618f0b9d4d3790eb7baaeb2a619d1e3528bf977704c8574ae56821e
Timestamp: 1658578867 Timestamp [UCT]: 2022-07-23 12:21:07 Age [y:d:h:m:s]: 03:167:01:59:38
Block: 549973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 899259 RingCT/type: yes/0
Extra: 01d74144fdb618f0b9d4d3790eb7baaeb2a619d1e3528bf977704c8574ae56821e02110000000133af99f4000000000000000000

1 output(s) for total of 9.240836338000 dcy

stealth address amount amount idx
00: c82347231620be6dda329aface9004990f6c8e5b7a5f814384e2e6a871a2af7d 9.240836338000 981406 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": 549983, "vin": [ { "gen": { "height": 549973 } } ], "vout": [ { "amount": 9240836338, "target": { "key": "c82347231620be6dda329aface9004990f6c8e5b7a5f814384e2e6a871a2af7d" } } ], "extra": [ 1, 215, 65, 68, 253, 182, 24, 240, 185, 212, 211, 121, 14, 183, 186, 174, 178, 166, 25, 209, 227, 82, 139, 249, 119, 112, 76, 133, 116, 174, 86, 130, 30, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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