Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a92c65b6a4304293687d37c4d77219c75df152b16a865423b66b5ce4cb3d5299

Tx prefix hash: 5118fcef969a0680b6899508b17c9a27ec5dbb78bb5c9fe54ddb21b5da801120
Tx public key: 39cb5c91a61bf4f6cdfa05d66a77956806213600bcebb1912298a99f6c4aa94d
Timestamp: 1705221686 Timestamp [UCT]: 2024-01-14 08:41:26 Age [y:d:h:m:s]: 01:063:22:56:11
Block: 935018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306810 RingCT/type: yes/0
Extra: 0139cb5c91a61bf4f6cdfa05d66a77956806213600bcebb1912298a99f6c4aa94d02110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28ff39e9cf71bf8b2d0c25bf78d958659ae9e2d1a26adb1380df0c8302ea37a6 0.600000000000 1393034 of 15

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": 935028, "vin": [ { "gen": { "height": 935018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28ff39e9cf71bf8b2d0c25bf78d958659ae9e2d1a26adb1380df0c8302ea37a6" } } ], "extra": [ 1, 57, 203, 92, 145, 166, 27, 244, 246, 205, 250, 5, 214, 106, 119, 149, 104, 6, 33, 54, 0, 188, 235, 177, 145, 34, 152, 169, 159, 108, 74, 169, 77, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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