Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8a6d2b05eef84ae923dd92efc7aec9889ae375a785b4ed54d73fcf52513d76d

Tx prefix hash: 23d863a37a7a1af1c8a9c8736f5dcf8a159777090dddc9ae7074474e128c7270
Tx public key: bd5ed6784966922571fd3bb9c940ccea9994a3bebfb8383f8bec38e1d390e7cd
Timestamp: 1695986146 Timestamp [UCT]: 2023-09-29 11:15:46 Age [y:d:h:m:s]: 01:189:16:52:10
Block: 858675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396626 RingCT/type: yes/0
Extra: 01bd5ed6784966922571fd3bb9c940ccea9994a3bebfb8383f8bec38e1d390e7cd021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.876704662000 dcy

stealth address amount amount idx
00: 0e0cd698d2ee646513e606a3f4bd7d6f467373767684ebcbf6dea88556821573 0.876704662000 1312861 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": 858685, "vin": [ { "gen": { "height": 858675 } } ], "vout": [ { "amount": 876704662, "target": { "key": "0e0cd698d2ee646513e606a3f4bd7d6f467373767684ebcbf6dea88556821573" } } ], "extra": [ 1, 189, 94, 214, 120, 73, 102, 146, 37, 113, 253, 59, 185, 201, 64, 204, 234, 153, 148, 163, 190, 191, 184, 56, 63, 139, 236, 56, 225, 211, 144, 231, 205, 2, 17, 0, 0, 0, 3, 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